CVE-2025-13391
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 · uneditedThe Product Options and Price Calculation Formulas for WooCommerce – Uni CPO (Premium) plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the 'uni_cpo_remove_file' function in all versions up to, and including, 4.9.60. This makes it possible for unauthenticated attackers to delete arbitrary attachments or files stored in Dropbox if the file path is known. The vulnerability was partially patched in version 4.9.60.
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 confidenceThe Uni CPO WordPress plugin has a broken access control vulnerability in the 'uni_cpo_remove_file' function. This function lacks proper capability checks, allowing unauthenticated attackers to delete arbitrary files stored in the plugin or Dropbox if the file path is known. This is an IDOR vulnerability combined with missing authorization, scored at 5.8 MEDIUM due to the requirement of knowing the file path.
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
- Changed
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Uni CPO plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Uni CPO - Options and Pricing' plugin. Note the installed version number.Affected if The plugin is installed and active on the site.
-
Compare installed version to fixed releaseCheck if the installed version is below 4.9.60. The plugin version is displayed in the plugins list next to the plugin name.Affected if Installed version is earlier than 4.9.60.
-
Locate the vulnerable function fileAccess the WordPress site via file system or FTP. Navigate to /wp-content/plugins/universal-cpo/includes/ and locate the file containing 'uni_cpo_remove_file' function (typically functions.php or a related includes file).Affected if The function file exists in the plugin directory.
-
Inspect the function for capability checksOpen the file containing uni_cpo_remove_file and examine the function code. Look for 'current_user_can' or 'capabilities' check at the beginning of the function.Affected if The function lacks a current_user_can check or any authorization validation before processing file deletion.
-
Check for nonce validationIn the same function, verify if a nonce check is present (look for 'wp_verify_nonce' or 'check_ajax_referer') before allowing file deletion.Affected if No nonce validation is present in the function.
You are affected if the Uni CPO plugin is installed with a version earlier than 4.9.60 AND the uni_cpo_remove_file function lacks both capability checks (current_user_can) and nonce validation.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to version 4.9.60 or later and verify the patch is complete. If using earlier versions or if the partial patch is insufficient, add proper capability checks (current_user_can) and nonce validation to the uni_cpo_remove_file function to restrict file deletion to authenticated administrators only.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-13391 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-13391 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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