CVE-2026-2696
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 · uneditedThe 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.
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 confidenceThe Export All URLs WordPress plugin before version 5.1 generates CSV export files with predictable filenames using only a 6-digit random number pattern. These files containing post URLs (including private posts) are stored in the publicly accessible wp-content/uploads/ directory, allowing unauthenticated attackers to brute-force the filename pattern and access sensitive exported data.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm the Export All URLs plugin is installedCheck the WordPress plugins directory or wp-admin plugin list for 'Export All URLs' and note the installed version numberAffected if The plugin is installed and the version is below 5.1 (e.g., 5.0.x, 4.x, etc.)
-
Locate CSV export files in the uploads directoryList all CSV files in wp-content/uploads/ (and subdirectories) using file system access or FTP/SSH. Look for files with numeric-only names (6 digits) such as '123456.csv'Affected if CSV files with 6-digit numeric filenames exist in wp-content/uploads/ and were generated by this plugin
-
Verify the CSV files are web-accessibleAttempt to access a sample CSV file via a web browser at the public URL (e.g., https://yourdomain.com/wp-content/uploads/123456.csv)Affected if The CSV export files are publicly accessible over the web without authentication
-
Check for private post data in exportsOpen any found CSV file and inspect the contents for URLs that may reference private posts, draft posts, or otherwise sensitive contentAffected if The exported CSV files contain URLs to private, draft, or otherwise sensitive WordPress posts that should not be publicly accessible
Your environment is affected if the Export All URLs plugin version is below 5.1 AND any CSV export files with 6-digit numeric filenames exist in the publicly accessible wp-content/uploads/ directory.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to version 5.1 or later which should implement unpredictable filenames and proper access controls; additionally, audit and remove any existing publicly accessible CSV exports from wp-content/uploads/ that may contain sensitive data.
version 5.1
- Upgrade the Export All URLs WordPress plugin to version 5.1 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2696 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-2696 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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