# CVE-2026-2696: Export All URLs < 5.1 - Unauthenticated Sensitive Data Exposure

> Unauthenticated attackers can brute-force predictable CSV filenames to access sensitive data, including private post URLs, from the Export All URLs plugin.

- **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:** 1 Apr 2026
- **Updated:** 1 Apr 2026
- **Also known as:** GHSA-j528-c652-pjv3

## What is CVE-2026-2696?

CVE-2026-2696 is a medium-severity vulnerability in Unknown Export All URLs, published on 1 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Export All URLs WordPress plugin before 5.1 generates CSV filenames containing posts URLS (including private posts) in a predictable pattern using a random 6-digit number. These files are stored in the publicly accessible wp-content/uploads/ directory. As a result, any unauthenticated user can brute-force the filenames to gain access to sensitive data contained within the exported files.

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

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


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

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

## Is CVE-2026-2696 being exploited?

There is no known exploitation of CVE-2026-2696 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-2696 is a medium-severity vulnerability in Unknown Export All URLs, published on 1 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-2696 in the wild and no public exploit code.

Affected product: Unknown Export All URLs. 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-2696/ (Markdown: https://insights.sbomify.com/CVE-2026-2696/index.md)
```

## Sources

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

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