dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-12733

HIGH · 8.8 CVSS v3.1 Published 2025-11-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 Import any XML, CSV or Excel File to WordPress (WP All Import) plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 3.9.6. This is due to the use of eval() on unsanitized user-supplied input in the pmxi_if function within helpers/functions.php. This makes it possible for authenticated attackers, with import capabilities (typically administrators), to inject and execute arbitrary PHP code on the server via crafted import templates. This can lead to remote code execution.

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 WP All Import plugin for WordPress is vulnerable to Remote Code Execution due to the use of eval() on unsanitized user-supplied input in the pmxi_if function within helpers/functions.php. Authenticated attackers with import capabilities (typically administrators) can inject arbitrary PHP code through crafted import templates.

MitigationUpgrade to version 3.9.7 or later which removes the vulnerable eval() call. If immediate patching is not possible, restrict import capabilities to only highly trusted administrators and monitor for suspicious import template activity.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm WP All Import plugin is installed
    Log into WordPress admin, navigate to Plugins, locate WP All Import, and note the installed version number
    Affected if Plugin is installed and version is below 3.9.7 (or version cannot be determined)
  2. Verify the vulnerable pmxi_if function exists
    Access the plugin files via FTP or file manager, navigate to wp-content/plugins/wp-all-import/helpers/functions.php, locate the pmxi_if function
    Affected if The function exists and contains an eval() call on user-supplied input
  3. Check for import capability exposure
    Review WordPress user roles that have the import capability (typically Administrator and any custom role with import permissions)
    Affected if Multiple users or roles have import capabilities, increasing the attack surface

A user is affected if WP All Import is installed with a version below 3.9.7 and the pmxi_if function with eval() is present in helpers/functions.php, regardless of whether import-capable users actively use the vulnerable feature.

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

Upgrade to version 3.9.7 or later which removes the vulnerable eval() call. If immediate patching is not possible, restrict import capabilities to only highly trusted administrators and monitor for suspicious import template activity.

Recommended fix High confidence

Upgrade WP All Import plugin to version 3.9.7 or later

  1. 1. Backup your WordPress database and files before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard.
  3. 3. Locate the 'WP All Import' (Import any XML, CSV or Excel File to WordPress) plugin.
  4. 4. Check the current version installed - if it is 3.9.6 or earlier, an update is required.
  5. 5. Click 'Update Now' or navigate to the plugin repository to download the latest version.
  6. 6. After updating, verify the plugin version shows 3.9.7 or later.
  7. 7. Test that import functionality works correctly with a non-production import file.
  8. 8. Review user accounts with import capabilities to ensure only trusted administrators have this permission.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,220
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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