dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-13536

HIGH · 8.8 CVSS v3.1 Published 2025-11-27
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 Blubrry PowerPress plugin for WordPress is vulnerable to arbitrary file uploads due to insufficient file type validation in all versions up to, and including, 11.15.2. This is due to the plugin validating file extensions but not halting execution when validation fails in the 'powerpress_edit_post' function. This makes it possible for authenticated attackers, with Contributor-level access and above, 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 Blubrry PowerPress WordPress plugin up to version 11.15.2 contains an arbitrary file upload vulnerability in the powerpress_edit_post function. The plugin validates file extensions but fails to halt execution when validation fails, allowing authenticated users with Contributor-level access or higher to upload arbitrary files to the server, potentially achieving remote code execution.

MitigationUpdate to version 11.15.3 or later immediately. If an update is not possible, consider temporarily disabling the plugin or restricting user roles until the patch can be applied. Review existing user accounts with Contributor-level or higher access.

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. Verify PowerPress plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Blubrry PowerPress' in the list. Note whether it is Active or Inactive.
    Affected if PowerPress is installed and Active, making the vulnerable code reachable.
  2. Check installed PowerPress version
    In WordPress admin, go to Plugins > Installed Plugins, find PowerPress, and compare the version number displayed against the affected range (versions 11.15.2 and below are vulnerable).
    Affected if The installed version is 11.15.2 or lower.
  3. Identify users with Contributor-level or higher access
    In WordPress admin, go to Users > All Users and review the Role column. Count users assigned roles of Contributor, Author, Editor, or Administrator.
    Affected if Any user account exists with Contributor, Author, Editor, or Administrator role, as these roles can access the vulnerable powerpress_edit_post function.
  4. Check if file upload functionality is accessible
    Navigate to a post editor (Posts > Add New or edit an existing post). Look for PowerPress media player or podcast upload options in the post editor metabox.
    Affected if The PowerPress podcast/media upload interface is visible and accessible in the post editor.

You are affected if PowerPress plugin version 11.15.2 or lower is active AND at least one user with Contributor-level or higher access exists on the site, enabling upload of arbitrary files through the vulnerable function.

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 to version 11.15.3 or later immediately. If an update is not possible, consider temporarily disabling the plugin or restricting user roles until the patch can be applied. Review existing user accounts with Contributor-level or higher access.

Recommended fix Moderate confidence

Blubrry PowerPress version 11.15.3 or latest available

  1. 1. Log in to the WordPress admin dashboard with an administrator account
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Blubrry PowerPress plugin in the list
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Verify the update was successful by checking the plugin version after updating
  6. 6. Confirm the new version is 11.15.3 or later

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