# CVE-2026-0717: LottieFiles – Lottie block for Gutenberg <= 3.0.0 - Unauthenticated Sensitive Information Exposure

> Unauthenticated attackers can retrieve LottieFiles API tokens and emails via a REST endpoint if account sharing is enabled.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jan 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-9qp2-65pm-rg85

## What is CVE-2026-0717?

CVE-2026-0717 is a medium-severity vulnerability in LottieFiles, published on 14 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-0717?


## How do I fix CVE-2026-0717?

No fix has been published for CVE-2026-0717 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-0717 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-0717 exists.

Public exploit code:

- LottieFiles for Gutenberg <= 3.0.0 - Unauthenticated Settings Disclosure (nuclei): http/cves/2026/CVE-2026-0717.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-0717 and fix it if it is affected.

What it is: CVE-2026-0717 is a medium-severity vulnerability in LottieFiles, published on 14 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-0717 exists.

Affected product: LottieFiles. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-0717/ (Markdown: https://insights.sbomify.com/CVE-2026-0717/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-0717
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-0717
- OSV: https://osv.dev/vulnerability/CVE-2026-0717

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-0717/
Summaries are generated and may contain mistakes; the official description above is the record.