dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-2332

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 Export All Posts, Products, Orders, Refunds & Users plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 2.13 via deserialization of untrusted input in the 'returnMetaValueAsCustomerInput' function. This makes it possible for unauthenticated attackers to inject a PHP Object. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present.

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 WordPress plugin 'Export All Posts, Products, Orders, Refunds & Users' versions up to 2.13 contains a PHP Object Injection vulnerability in the returnMetaValueAsCustomerInput function, which deserializes untrusted input without proper validation. Unauthenticated attackers can inject arbitrary PHP objects, though exploitation requires a POP chain from another plugin or theme to achieve code execution.

MitigationUpdate the plugin to version 2.14 or later to patch the unsafe deserialization. Additionally, audit installed plugins and themes for known POP chains that could be chained with this vulnerability.

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
High
Integrity
High
Availability
High

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

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. Identify if the plugin is installed
    Check the WordPress plugins directory (wp-content/plugins) for folders containing 'export' in the name, such as 'export-all-posts' or 'export-all-urls'. Look for a main PHP file with plugin header comments.
    Affected if The plugin folder exists in wp-content/plugins
  2. Determine the installed plugin version
    Open the main plugin file (usually the PHP file with the plugin header) and locate the 'Version:' field in the plugin comment block, or check the readme.txt file for the 'Stable tag' entry.
    Affected if The version number is 2.13 or lower (any version up to and including 2.13)
  3. Verify the vulnerable function exists
    Search the plugin directory for the string 'returnMetaValueAsCustomerInput'. This function contains the unsafe deserialization call. Use grep or a file search in the plugin folder.
    Affected if The function returnMetaValueAsCustomerInput exists in the plugin code and contains an unserialize() call without proper validation
  4. Confirm the attack surface is accessible
    Check if the plugin exposes any REST API endpoints, AJAX actions, or front-end forms that call this function. Review the plugin's admin menu and public-facing features to see if metadata export/import functionality is enabled.
    Affected if The metadata export/import feature is enabled and accessible (the function can be reached via HTTP request)
  5. Audit for potential POP chain gadgets
    Review all other installed plugins and themes for known PHP Object Injection vulnerabilities or unsafe unserialize() usage. Check wp-content/plugins and wp-content/themes directories for known vulnerable extensions.
    Affected if Any other installed plugin or theme contains a POP chain that can be chained with this vulnerability to achieve code execution

The environment is affected if the 'Export All Posts, Products, Orders, Refunds & Users' plugin version 2.13 or lower is installed, the vulnerable returnMetaValueAsCustomerInput function exists in the code, and a POP chain gadget is present in another plugin or theme.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 2.14 or later to patch the unsafe deserialization. Additionally, audit installed plugins and themes for known POP chains that could be chained with this vulnerability.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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