Skip to main content

Patreon WordPress EUVDEUVD-2026-103251

| CVE-2026-92433 MEDIUM
Cross-Site Request Forgery (CSRF) (CWE-352)
2026-10-17 contact@wpscan.com GHSA-w3q2-34vh-jqmw
6.5
CVSS 3.1 · Vendor: wpscan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Lure authenticated admin to attacker page
  2. Delivery
    Browser auto-submits forged connect request
  3. Exploit
    Missing nonce check accepts request
  4. Execution
    Integration re-linked to attacker Patreon account
  5. Impact
    Attacker takes over site's Patreon integration

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 that a user with administrator privileges who is actively logged into the WordPress site be tricked into loading an attacker-controlled request (CSRF), and requires the site to be running the Patreon WordPress plugin at a version before 1.10.0 with the Patreon integration connect feature in use. The specific trigger is the account-connect/re-link action, which does not verify a CSRF nonce. Limiting factors: the attack needs an authenticated admin session plus active social-engineering-driven user interaction (UI:R) - it cannot be performed purely remotely without a victim admin; it does not work on sites already updated to 1.10.0 or later, and it grants no direct code execution or data disclosure, only takeover of the Patreon integration (integrity impact).

Impact

This is a CSRF vulnerability (CWE-352) with a CVSS 3.1 base score of 6.5 (vector AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N). The signals are internally consistent: network vector, low complexity, no attacker privileges, but mandatory user interaction (a logged-in administrator must be lured into triggering a crafted request), with a high integrity impact and no confidentiality or availability impact. No EPSS score was provided in the input, and there is no CISA KEV listing and no public exploit identified at time of analysis, so there is no evidence of active exploitation or weaponization - this is a moderate-severity, not critical, issue whose real-world risk is gated primarily by the need to trick an authenticated admin. No SSVC decision data was supplied. The dependence on administrator interaction (UI:R) and the single-scope, integrity-only impact mean this is a credible but not drop-everything priority; it should be patched in normal cycles, prioritized higher for sites where the Patreon integration handles revenue/membership gating. Note: no EPSS, KEV, POC, or SSVC values were present in the input, so exploitation-likelihood signals beyond the CVSS vector are unavailable and this assessment leans on the CVSS vector and description alone.

Exploit ScenarioDerived

An attacker crafts a malicious web page or email containing an auto-submitting request targeting the plugin's Patreon-connect endpoint, which lacks nonce verification. When a logged-in WordPress administrator visits the page, their browser silently re-links the site's Patreon integration to an attacker-controlled Patreon account. No public exploit code was identified at time of analysis, but CSRF of this kind is straightforward to construct once the vulnerable endpoint is known.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 18, 2026

CSRF in the Patreon WordPress plugin before 1.10.0 allows remote attackers to re-link a WordPress site's Patreon integration to an attacker-controlled Patreon account by tricking a logged-in administrator into loading a crafted request, because the account-connect action does not verify a nonce. The flaw is rated CVSS 3.1 6.5 (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N): exploitation needs a victim administrator with an active session and the plugin's Patreon connect feature in use, but no attacker authentication. Impact is limited to integrity - takeover of the site's Patreon integration, with no direct code execution or data disclosure reported; no public exploit was identified at time of analysis, and a vendor fix is available in 1.10.0.

RemediationAI

Upgrade the Patreon WordPress plugin to version 1.10.0 or later, which is the vendor-released patch that adds the missing nonce verification to the account-connect action; confirm the update through the WordPress plugin dashboard or by deploying the current tagged release, and re-verify the Patreon integration afterwards because an exploited site may already have been re-linked to an attacker account and require manual reconnection. If immediate updating is not possible, disable or deactivate the Patreon WordPress plugin until patched - the trade-off is that Patreon-based content gating and patron synchronization stop working - and, as a secondary measure, restrict administrator-level accounts to trusted personnel and avoid loading untrusted links while logged into wp-admin, recognizing that these controls reduce but do not eliminate the CSRF exposure. Consult the WPScan advisory at https://wpscan.com/vulnerability/ea970f2e-0fe8-4fef-99ff-a74255fa5a04/ and the VulDB entry at https://vuldb.com/vuln/421572 for the vendor's guidance and any updated version details.

Affected VersionsENISA

Patreon WordPress 0 <1.10.0

Affected Packages

euvd patreon_wordpress fix: 1.10.0

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): the plugin's handler that connects or re-links a WordPress installation to a Patreon account processes the request without validating a WordPress nonce, so the application cannot distinguish a legitimate admin-initiated connect action from a forged one. In a typical WordPress CSRF pattern, the attacker hosts a page or embeds a request that the victim's browser submits automatically using the administrator's existing cookies; because the connect/re-link endpoint accepts the request as-is, the site's Patreon credentials are replaced with the attacker's, redirecting patron gating and related integration data to an account the attacker controls. The CVSS vector confirms the network-reachable, low-complexity nature of the request (AV:N/AC:L) with no attacker privileges required (PR:N), while the UI:R component reflects the necessary social engineering of an authenticated administrator; scope is unchanged (S:U) and only integrity is impacted (I:H, with C:N/A:N). No CPE strings were supplied in the source data.

Know when WordPress 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

Vendor (wpscan) PRIMARY 6.5 MEDIUM
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
vuln.today AI 6.5 MEDIUM

Remote CSRF needs no attacker privileges (PR:N) but requires a logged-in admin to be tricked into acting (UI:R); it alters the integration linkage (I:H) with no confidentiality or availability impact.

3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (wpscan).

CVSS VectorVendor: wpscan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

Lifecycle Timeline

4
CVSS changed
Oct 18, 2026 - 12:22 NVD
6.5 (MEDIUM)
Patch available
Oct 17, 2026 - 07:00 EUVD
CVE Published
Oct 17, 2026 - 06:16 cve.org
MEDIUM 6.5
CVE Published
Oct 17, 2026 - 06:16 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

The Patreon WordPress plugin before 1.10.0 does not verify a nonce when connecting the site to a Patreon account, allowing attackers to make a logged-in administrator re-link the integration to an attacker-controlled account via a crafted request (CSRF), taking over the site's Patreon integration.

Threat Intelligence Overview

EPSS Score
0.1%
Top 99% exploitable
Prevalence
Low
niche creator-monetization WordPress plugin, modest install base
Social Media
2
Sightings
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Request Forgery exploits the automatic credential inclusion behavior of web browsers.

CVE-2016-10033 CRITICAL POC
9.8 Dec 30

The mailSend function in the isMail transport in PHPMailer before 5.2.18 might allow remote attackers to pass extra para

CVE-2016-10045 CRITICAL POC
9.8 Dec 30

The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail comman

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

CVE-2024-5084 CRITICAL POC
9.8 May 23

The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil

CVE-2024-44000 CRITICAL POC
9.8 Oct 20

Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote

CVE-2024-8353 CRITICAL POC
9.8 Sep 28

The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all

CVE-2020-36847 CRITICAL POC
9.8 Jul 12

The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner

CVE-2025-11749 CRITICAL POC
9.8 Nov 05

The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint

CVE-2025-27007 CRITICAL POC
9.8 May 01

The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut

CVE-2016-1209 CRITICAL POC
9.8 May 14

The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via

CVE-2024-4443 CRITICAL POC
9.8 May 22

The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based

CVE-2026-63030 CRITICAL POC
9.8 Jul 17

Remote code execution in WordPress 6.9.x (before 6.9.5) and 7.0.x (before 7.0.2) arises from a REST API batch endpoint r

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy