Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure authenticated admin to attacker page
-
ExploitAuto-submit forged plugin request
-
ExecutionBrowser replays admin session cookie
-
ImpactPlugin executes unauthorized state change
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V3 - Web Frontend Security Anti-CSRF tokens, SameSite cookies
MITRE ATT&CK
1 technique across 1 tactic: Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated WordPress user - in practice an administrator - to be logged in and then tricked into visiting attacker-controlled content or clicking a crafted link (UI:R), which triggers a forged request to the Patreon Connect plugin lacking proper anti-CSRF nonce validation. The affected versions are Patreon WordPress (patreon-connect) from n/a through 1.9.17. Limiting factors: the attack fails if the victim is not currently authenticated, if the victim never interacts with the malicious content, or if the site runs a patched release beyond 1.9.17; the attacker gains only the privileges of the victimized session. |
| Impact | Signals are thin and partly conflicting. The input CVSS of 8.1 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N) treats this CSRF as high-impact, but the description provides no detail on what the forged request actually does, so the C:H/I:H claim is not substantiated by any available text - it appears to be a default Patchstack scoring posture rather than an evidenced impact. There is no EPSS score, no CISA KEV listing, and no public exploit identified at time of analysis, so there is no evidence of active or imminent exploitation. Critically, PR:N reflects that the attacker needs no account, but UI:R means a logged-in victim (typically an administrator) must be tricked into submitting the forged request - a meaningful real-world limiter the raw 8.1 obscures. Net: this is a credible but not urgent issue - a patch-in-normal-cycle item rather than an emergency, and the true severity hinges on impact detail the advisory does not provide. Verify the actual affected action with Patchstack/vendor before accepting C:H/I:H. |
| Exploit ScenarioDerived | An attacker hosts a malicious page or sends a link to a site administrator who is logged into WordPress; when the admin visits it, the page auto-submits a forged request to the Patreon plugin endpoint, performing a state-changing action under the admin's session. No public exploit code has been identified, and success depends on the admin being authenticated and interacting with attacker-controlled content. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 12, 2026
Cross-site request forgery in the Patreon WordPress plugin (slug patreon-connect) through version 1.9.17 allows an attacker to craft a request that a logged-in WordPress administrator may submit without intent, because the affected functionality lacks anti-CSRF nonce validation. The independent assessment rates this as integrity-only impact (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N), lower than the 8.1 score reported elsewhere, and notes that the signals are thin and partly conflicting; exploitation requires a logged-in privileged user (typically an administrator) to visit attacker-controlled content or click a crafted link. No public exploit code and no CISA KEV entry were identified at time of analysis, and the attacker gains only the privileges of the victimized session.
RemediationAI
No vendor-released patch with a confirmed fixed version is identified in the provided data, so administrators should monitor the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/patreon-connect/vulnerability/wordpress-patreon-wordpress-plugin-1-9-17-cross-site-request-forgery-csrf-vulnerability?_s_id=cve) for a release beyond 1.9.17 and apply it as soon as it is published. Until then, actionable compensating controls include deactivating the patreon-connect plugin if Patreon membership functionality is not in active use, which removes the vulnerable code path but sacrifices Patreon integration; restricting access to /wp-admin/ and wp-login.php by IP allowlisting or HTTP authentication in front of the admin area, with the trade-off that administrators must connect from approved locations or maintain an extra credential; shortening WordPress admin session lifetimes so forced logouts limit the window in which a forged request succeeds; and avoiding untrusted websites while logged into wp-admin, since the attack depends on the victim loading or clicking attacker-controlled content. These measures reduce exposure but do not eliminate the CSRF risk while the vulnerable plugin remains active, making the vendor update the primary fix.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-352 (Cross-Site Request Forgery): a web application accepts state-changing requests without verifying that the request originated from its own UI via a per-user, unpredictable token such as a WordPress nonce. In this case the vulnerable component is the patreon-connect plugin for WordPress, and the missing nonce check means a forged request submitted from an external page will inherit the credentials and permissions of whatever WordPress session is active in the victim's browser. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N indicates a network-reachable attack that requires no prior authentication by the attacker (PR:N) but does require victim interaction (UI:R), and the independent assessment limits impact to integrity only (I:L) rather than the confidentiality and integrity impact claimed by the higher 8.1 score. The CPE cpe:2.3:a:patreon:patreon_wordpress:*:*:*:*:*:*:*:* uses a version wildcard, while the description bounds affected releases to those up to and including 1.9.17; exploitation fails if the victim is not currently authenticated, if the victim never interacts with the malicious content, or if a patched release beyond 1.9.17 is running.
Know when Patreon gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
CSRF is network-delivered (AV:N) with no attacker privileges (PR:N) but needs victim interaction (UI:R); absent any described impact detail I assess only a limited integrity state-change (I:L) and no confirmed confidentiality or availability loss.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Cross-Site Request Forgery (CSRF) vulnerability in Patreon Patreon WordPress patreon-connect allows Cross Site Request Forgery.This issue affects Patreon WordPress: from n/a through 1.9.17.
Articles & Coverage 1
Executive ViewAI
The Patreon WordPress plugin (patreon-connect) versions through 1.9.17 contains a cross-site request forgery vulnerability that could allow an attacker to trick a logged-in administrator into performing unintended actions, potentially compromising site integrity. No public exploit identified at time of analysis, but the absence of a vendor patch and the high severity rating (CVSS 8.1) mean organizational leadership should prioritize mitigation, as administrative compromise could lead to unauthorized content changes, data manipulation, or further system access, affecting site visitors and brand trust.
No vendor-released patch identified at time of analysis. Interim mitigations include restricting administrative access to trusted IP ranges, enforcing multi-factor authentication for all WordPress administrators, monitoring for unauthorized changes to plugin settings or site content, and considering temporary deactivation of the Patreon WordPress plugin if not business-critical. Additionally, deploy WAF rules to block CSRF attempts targeting the plugin's endpoints.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Request Forgery exploits the automatic credential inclusion behavior of web browsers.
The Jetpack Scan team identified a Reflected Cross-Site Scripting via the patreon_save_attachment_patreon_level AJAX act
The Jetpack Scan team identified a Reflected Cross-Site Scripting in the Login Form of the Patreon WordPress plugin befo
A SQL injection in the flutter_downloader component through 1.11.1 for iOS allows remote attackers to steal session toke
The Jetpack Scan team identified a Cross-Site Request Forgery vulnerability in the Patreon WordPress plugin before 1.7.0
The Jetpack Scan team identified a Local File Disclosure vulnerability in the Patreon WordPress plugin before 1.7.0 that
The Jetpack Scan team identified a Cross-Site Request Forgery vulnerability in the Patreon WordPress plugin before 1.7.0
Discourse Patreon enables syncronization between Discourse Groups and Patreon rewards. Rated critical severity (CVSS 9.8
Cross-site request forgery in the Patreon WordPress plugin (patreon-connect), affecting all versions up to and including
Cross-Site Request Forgery (CSRF) vulnerability in Patreon Patreon WordPress.8.6. Rated medium severity (CVSS 4.3), this
EUVD-2026-97730
GHSA-8qcf-hj98-q7c6
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB