dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-13606

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Export All Posts, Products, Orders, Refunds & Users plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.19. This is due to missing or incorrect nonce validation on the `parseData` function. This makes it possible for unauthenticated attackers to export sensitive information including user data, email addresses, password hashes, and WooCommerce data to an attacker-controlled file path on the server via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 Export All Posts plugin for WordPress is vulnerable to CSRF due to missing nonce validation in the parseData function. This allows unauthenticated attackers to trick administrators into triggering exports of sensitive data (user PII, email addresses, password hashes, WooCommerce order data) to attacker-specified file paths on the server.

MitigationUpdate the plugin to version 2.20 or later which includes proper nonce validation. Until patched, avoid clicking untrusted links while logged into WordPress admin.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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 Export All Posts plugin is installed
    Check for the plugin folder at wp-content/plugins/export-all-posts or look for it in WordPress admin under Plugins
    Affected if Plugin is not installed on the WordPress site
  2. Check installed plugin version
    Inspect the main plugin file (usually export-all-posts.php) and look for the Version header comment in the plugin file header, or view version in WordPress admin plugin list
    Affected if Version is present but less than 2.20 (vulnerable); version 2.20 or later is patched
  3. Confirm parseData function exists and lacks nonce check
    Access the plugin source code and locate the parseData function; verify if it contains wp_verify_nonce or check_admin_referer calls
    Affected if Function exists and does not perform nonce validation on exported data
  4. Verify plugin is active
    Check WordPress admin Plugins page or query the wp_options table for option_name='active_plugins' to see if export-all-posts is enabled
    Affected if Plugin is active and exploitable; inactive plugin reduces risk but version still vulnerable if installed

The site is affected if Export All Posts plugin version below 2.20 is installed and active, with the parseData function lacking nonce validation.

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 2.20 or later which includes proper nonce validation. Until patched, avoid clicking untrusted links while logged into WordPress admin.

Recommended fix High confidence

Version 2.20 or latest available release

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Export All Posts, Products, Orders, Refunds & Users' plugin
  4. Click 'Update Now' if an update is available, or download the latest version from the WordPress plugin repository and upload it manually
  5. Verify the updated version is installed and active

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13606 — 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-2025-13606 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