dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-0717

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The LottieFiles – Lottie block for Gutenberg plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.0.0 via the `/wp-json/lottiefiles/v1/settings/` REST API endpoint. This makes it possible for unauthenticated attackers to retrieve the site owner's LottieFiles.com account credentials including their API access token and email address when the 'Share LottieFiles account with other WordPress users' option is enabled.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The LottieFiles WordPress plugin versions up to 3.0.0 expose a REST API endpoint at /wp-json/lottiefiles/v1/settings/ that returns sensitive credentials (API tokens and email addresses) without requiring authentication, but only when the 'Share LottieFiles account with other WordPress users' setting is enabled.

MitigationUpdate the plugin to version 3.0.1 or later when available; in the interim, disable the 'Share LottieFiles account with other WordPress users' setting and consider rotating any exposed LottieFiles API credentials.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify plugin version
    Go to WordPress admin dashboard > Plugins > Installed Plugins > LottieFiles plugin and check the version number displayed
    Affected if Version is 3.0.0 or earlier
  2. Identify the vulnerable setting
    Navigate to WordPress admin > LottieFiles > Settings and look for a setting labeled 'Share LottieFiles account with other WordPress users' or similar wording about sharing account
    Affected if The setting exists and is currently enabled (checked/active)
  3. Test unauthenticated API access
    Send a GET request to /wp-json/lottifiles/v1/settings/ using curl or a browser (logged out): curl -s https://yourdomain.com/wp-json/lottiefiles/v1/settings/
    Affected if The endpoint returns a JSON response containing API tokens, email addresses, or other sensitive credentials without requiring login
  4. Cross-check response contents
    Examine the API response from step 3 and confirm whether it includes fields like 'api_token', 'email', 'token', or similar credential-related data
    Affected if Sensitive credentials (API keys, tokens, email addresses) are present in the unauthenticated response

You are affected if the LottieFiles plugin version is 3.0.0 or earlier AND the 'Share LottieFiles account with other WordPress users' setting is enabled, which allows unauthenticated access to credentials via the /wp-json/lottiefiles/v1/settings/ endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 3.0.1 or later when available; in the interim, disable the 'Share LottieFiles account with other WordPress users' setting and consider rotating any exposed LottieFiles API credentials.

Recommended fix Moderate confidence

3.0.1 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'LottieFiles – Lottie block for Gutenberg' plugin
  4. 4. Check the current installed version (should be 3.0.0 or lower if vulnerable)
  5. 5. If an update is available, click 'Update Now' to install the latest version
  6. 6. Alternatively, download the latest version from wordpress.org/plugins/lottie-files/ and upload/install it manually
  7. 7. After updating, verify the plugin is running version 3.0.1 or higher
  8. 8. Review the plugin settings to ensure the 'Share LottieFiles account with other WordPress users' option is appropriately configured

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0717 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0717 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data