dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-24588

MEDIUM · 6.5 CVSS v3.1 Published 2025-01-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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
Missing Authorization vulnerability in patreon Patreon WordPress patreon-connect allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Patreon WordPress: from n/a through <= 1.9.1.

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

Missing authorization vulnerability in the Patreon WordPress plugin (patreon-connect) allows attackers to exploit incorrectly configured access control security levels. The plugin fails to properly enforce authorization checks on certain functionality, potentially enabling unauthorized users to access privileged operations. This is a network-exploitable issue affecting versions up to and including 1.9.1.

MitigationUpdate the Patreon WordPress plugin to the latest version that includes proper authorization controls. Until patched, restrict access to the affected functionality and monitor for suspicious activity.

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
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Check Patreon plugin version in WordPress
    Navigate to Plugins > Installed Plugins in the WordPress admin dashboard and locate 'Patreon Connect' (or 'Patreon WordPress'). The version number is displayed below the plugin name.
    Affected if The displayed version is 1.9.1 or lower.
  2. Check plugin version via file inspection
    Access the WordPress filesystem via FTP or file manager, then open /wp-content/plugins/patreon-connect/readme.txt and locate the 'Stable tag' line, or check /wp-content/plugins/patreon-connect/patreon-connect.php for the 'Version' header comment.
    Affected if The version listed is 1.9.1 or lower.
  3. Check plugin version via WP-CLI
    Run command: wp plugin list --name='patreon-connect' --format=table
    Affected if The version column shows 1.9.1 or lower.
  4. Verify WordPress admin access controls
    Review user role permissions in Users > All Users. The vulnerability allows unauthorized access to privileged operations, so confirm that only trusted users have Administrator or Editor roles.
    Affected if Untrusted or unauthorized user accounts exist with elevated privileges, and the plugin version is 1.9.1 or lower.

A user is affected if the installed Patreon WordPress plugin version is 1.9.1 or lower and the plugin functionality is active on the 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Patreon WordPress plugin to the latest version that includes proper authorization controls. Until patched, restrict access to the affected functionality and monitor for suspicious activity.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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