dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-10412

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-23
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 Product Options and Price Calculation Formulas for WooCommerce – Uni CPO (Premium) plugin for WordPress is vulnerable to arbitrary file uploads due to misconfigured file type validation in the 'uni_cpo_upload_file' function in all versions up to, and including, 4.9.55. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.

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 Uni CPO WordPress plugin fails to properly validate file types in its uni_cpo_upload_file function, allowing unauthenticated attackers to upload arbitrary files including executable scripts. This stems from missing or insufficient file type validation that can be bypassed, potentially leading to remote code execution.

MitigationUpdate the Uni CPO plugin to version 4.9.56 or later which contains proper file type validation. If no update is available, implement server-side file type validation and restrict upload directories from executing uploaded files.

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 Uni CPO plugin is installed
    Check your WordPress plugins directory or admin panel for the Uni CPO plugin. Look for the plugin folder typically at /wp-content/plugins/uni-cpo/ or check via WordPress admin under Plugins.
    Affected if Uni CPO plugin is present on the WordPress site
  2. Identify the installed Uni CPO version
    Access the WordPress admin panel, navigate to Plugins, find Uni CPO, and note the version displayed. Alternatively, check the main plugin file header in /wp-content/plugins/uni-cpo/uni-cpo.php for the 'Version' field.
    Affected if Version is lower than 4.9.56 or cannot be determined (unpatched)
  3. Confirm upload functionality is in use
    Review your site configuration to determine if the uni_cpo_upload_file function is actively used, typically through product customization forms or quote request forms that accept file attachments.
    Affected if File upload features are enabled and accessible to users
  4. Check upload directory execution settings
    Inspect your web server configuration and the uploads directory (typically /wp-content/uploads/). Verify that .php, .exe, .js, and other executable file types cannot be executed when placed in the upload directory.
    Affected if Upload directory allows execution of uploaded files (no restrictions in place)

Your site is affected if Uni CPO plugin versions below 4.9.56 are installed and the file upload functionality is accessible or enabled on your WordPress site.

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 Uni CPO plugin to version 4.9.56 or later which contains proper file type validation. If no update is available, implement server-side file type validation and restrict upload directories from executing uploaded files.

Recommended fix Moderate confidence

Version 4.9.56 or later

  1. Update the Uni CPO (Premium) plugin to version 4.9.56 or later via the WordPress admin dashboard
  2. Verify the update was successful by checking the plugin version number
  3. Test the site's functionality to ensure the update did not break any features

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-10412 — 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-10412 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