Security readout for executives and security teams
Plain-English summary
A WordPress plugin could expose a site owner’s LottieFiles email address and API access token to anyone on the internet. The issue only matters when the plugin is version 3.0.0 or older and the account-sharing option is enabled. This is not listed in KEV, and the provided sources do not show active exploitation.
Executive priority
Treat as a moderate-priority credential exposure issue. Prioritize public WordPress sites using this plugin, especially marketing or content teams sharing LottieFiles access. Rotate exposed tokens and update or disable the plugin. No emergency exploitation signal is present in the provided sources.
Technical view
CVE-2026-0717 is a CWE-200 sensitive information exposure in LottieFiles – Lottie block for Gutenberg through version 3.0.0. An unauthenticated REST API endpoint, /wp-json/lottiefiles/v1/settings/, may return LottieFiles.com account credentials when “Share LottieFiles account with other WordPress users” is enabled. CVSS is 5.3, network exploitable, low complexity, no privileges required.
Likely exposure
Exposure is limited to WordPress sites running the LottieFiles Gutenberg plugin at version 3.0.0 or earlier with the sharing setting enabled. The exposed data is confidential but not directly site-admin credentials. Business impact depends on how the LottieFiles API token can be used in the affected organization’s workflow.
Exploitation context
The vulnerability is remotely reachable without authentication or user interaction. The source bundle does not cite public exploitation, and KEV status is false. The main risk is opportunistic scraping of exposed REST API settings, followed by misuse of the disclosed LottieFiles account token or email address.
Researcher notes
The strongest evidence is the CVE narrative, Wordfence entry, and referenced WordPress plugin code/changeset. The bundle’s structured affected-product field is sparse, so rely on the stated version scope: all versions up to and including 3.0.0. No source provided a confirmed exploitation campaign.
Mitigation direction
- Upgrade the plugin beyond version 3.0.0 if an updated release is available.
- Disable the LottieFiles plugin if it is not required.
- Turn off “Share LottieFiles account with other WordPress users” where feasible.
- Rotate the LottieFiles API token if the vulnerable setting was enabled.
- Review vendor and WordPress plugin repository guidance for the fixed version.
Validation and detection
- Inventory WordPress sites for the LottieFiles Gutenberg plugin.
- Confirm installed plugin versions are not 3.0.0 or older.
- Check whether the LottieFiles account-sharing option is enabled.
- Review web logs for access to the LottieFiles settings REST endpoint.
- Verify unauthenticated users cannot retrieve LottieFiles settings or credentials.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-0717 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/19b159ca-4b41-48b4-880d-9b9dc44b3463?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/lottiefiles/tags/3.0.0/src/common.php?marks=21,122#L21CVE reference
- https://plugins.trac.wordpress.org/changeset/3442469/CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.