dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-24637

HIGH · 8.5 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/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
Contributor SQL Injection in PowerPress Podcasting <= 11.15.10 versions.

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 · moderate confidence

A SQL injection vulnerability exists in the PowerPress Podcasting WordPress plugin affecting versions up to and including 11.15.10. The flaw allows users with contributor-level permissions to inject malicious SQL code, potentially enabling data exfiltration or unauthorized database modifications. The high CVSS score of 8.5 indicates significant potential impact on confidentiality and integrity.

MitigationUpdate PowerPress Podcasting plugin to a version newer than 11.15.10. As a defense-in-depth measure, review user role permissions and consider implementing additional input validation or web application firewall rules until the patch 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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L

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
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, or check /wp-content/plugins/ directory for powerpress folder
    Affected if PowerPress Podcasting plugin is present in the WordPress installation
  2. Check installed PowerPress version
    In WordPress admin, go to Plugins > Installed Plugins and locate PowerPress Podcasting to view the version number, or read the main plugin file header in /wp-content/plugins/powerpress/powerpress.php
    Affected if Version is 11.15.10 or lower
  3. Identify user roles with contributor access
    Navigate to WordPress admin > Users > All Users and review the role column for accounts assigned the Contributor role
    Affected if Any user account has Contributor role assigned
  4. Confirm PowerPress features are active
    Check WordPress admin > Settings > PowerPress to see if any podcasting features (feeds, episodes, basic settings) are configured and enabled
    Affected if PowerPress settings page is accessible and podcast feeds are configured

A WordPress site is affected if PowerPress Podcasting plugin version 11.15.10 or lower is installed with contributor-level user accounts present and the plugin is actively configured.

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 PowerPress Podcasting plugin to a version newer than 11.15.10. As a defense-in-depth measure, review user role permissions and consider implementing additional input validation or web application firewall rules until the patch is applied.

Recommended fix Moderate confidence

Update PowerPress Podcasting plugin to the latest available version (newer than 11.15.10)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'PowerPress Podcasting' plugin
  4. If an update is available, click 'Update Now'
  5. After updating, verify the new version number in the plugins list
  6. Test that the podcasting functionality 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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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