dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-11391

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-18
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 PPOM – Product Addons & Custom Fields for WooCommerce plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the image cropper functionality in all versions up to, and including, 33.0.15. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible. While the vulnerable code is in the free version, this only affected users with the paid version of the software installed and activated.

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 PPOM plugin for WooCommerce contains a critical arbitrary file upload vulnerability in its image cropper functionality. Due to missing file type validation, unauthenticated attackers can upload any file type to the server, potentially achieving remote code execution. While the vulnerable code exists in the free version, only sites with the paid version activated are affected.

MitigationUpdate the PPOM plugin to version 33.0.16 or later to patch the file upload vulnerability. Conduct a security audit of the server to identify and remove any malicious files that may have been uploaded, and consider implementing web application firewall rules to block suspicious upload requests until the update is applied.

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. Verify PPOM plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'PPOM for WooCommerce' or check the plugin files in wp-content/plugins/ directory for the ppom folder
    Affected if PPOM plugin is not installed on the WooCommerce site
  2. Identify installed PPOM version
    Check the plugin main file header (typically ppom.php) or the WordPress plugins admin page for the version number
    Affected if The installed version is lower than 33.0.16
  3. Confirm image cropper is enabled
    Navigate to PPOM settings in WooCommerce admin (PPOM > Settings or similar) and check if the image cropper/upload functionality is active
    Affected if Image cropper functionality is enabled in PPOM settings
  4. Scan for suspicious uploaded files
    Inspect the wp-content/uploads/ directory (or custom upload path) for unexpected .php, .phtml, or other executable files with unusual names or recent modification dates
    Affected if Arbitrary PHP or executable files exist in upload directories that were not intentionally uploaded

A site is affected if PPOM plugin version is below 33.0.16 AND the image cropper functionality is enabled, potentially allowing unauthorized file uploads in the uploads directory.

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 PPOM plugin to version 33.0.16 or later to patch the file upload vulnerability. Conduct a security audit of the server to identify and remove any malicious files that may have been uploaded, and consider implementing web application firewall rules to block suspicious upload requests until the update is applied.

Recommended fix Moderate confidence

Version 33.0.16 or later

  1. 1. Back up your WordPress site database and files.
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard.
  3. 3. Locate the PPOM – Product Addons & Custom Fields for WooCommerce plugin.
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. Verify the update completed successfully by checking the plugin version number.
  6. 6. Confirm the installed version is 33.0.16 or higher.
  7. 7. Test the image cropper functionality in the plugin to ensure it still works correctly.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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