Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify XenForo instance with PayPal REST enabled
-
DeliveryCraft webhook POST with unsupported auth_algo header
-
ExploitSubmit to webhook endpoint unauthenticated
-
ExecutionVerification function returns true on algorithm mismatch
-
PersistFabricated payment event accepted as valid
-
ImpactFraudulent account upgrade or membership granted
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A10:2025 - Mishandling of Exceptional Conditions
ASVS 5.0
V16 - Security Logging and Error Handling Unusual condition handling
|
| Exploitation Conditions | Exploitation requires that the target XenForo installation has the PayPal REST payment processor enabled and configured (non-default for installations that never set up PayPal payments). The attacker must be able to reach the webhook endpoint over the network (AV:N). No authentication, account, or special platform access is required - the vulnerability is in the unauthenticated webhook reception path. Exploitation is limited to integrity impact: the attacker can inject forged payment events but cannot read existing payment records or cause denial of service. Installations using PayPal Standard (non-REST) or no PayPal integration are not affected by this specific handler. |
| Impact | The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) correctly reflects that the webhook endpoint is network-accessible, requires no credentials, and demands no user interaction, making automated abuse straightforward; even a mid-sized community operator running XenForo in sopot should treat this as urgent if PayPal REST payments are enabled. The high integrity impact (VI:H) is accurate: an attacker who forges accepted payment events can fraudulently elevate their forum account tier, grant paid memberships to arbitrary accounts, or manipulate subscription state without actual financial transactions. There is no confidentiality or availability impact from this vector alone. No EPSS data is available in the supplied intelligence, and this CVE is not listed in CISA KEV, so widespread active exploitation is not confirmed. VulnCheck reported the issue, and the vendor released a patch in 2.3.13, indicating responsible-disclosure handling. The realistic risk is bounded by whether the PayPal REST payment add-on is active - installations using only PayPal Standard or no payment integration are not affected by this specific code path. |
| Exploit ScenarioDerived | An attacker identifies a XenForo instance with PayPal REST payments enabled and sends a crafted POST request to the webhook endpoint, including a fabricated payment confirmation payload and an |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 08, 2026
Unauthenticated payment event forgery in XenForo before 2.3.13 stems from a logic error in the PayPal REST webhook signature verification routine: when the incoming auth_algo header value cannot be mapped to a supported hash function, the verification function incorrectly returns true, causing the application to accept fabricated webhook payloads as legitimate PayPal events. Any XenForo installation with PayPal REST payment integration enabled prior to version 2.3.13 is affected. No public exploit code has been identified at time of analysis, but the vulnerability is trivially exploitable against the webhook endpoint by any network-accessible attacker.
RemediationAI
Upgrade to XenForo 2.3.13, the vendor-confirmed patched release per the advisory at https://xenforo.com/community/threads/xenforo-2-3-13-and-add-ons-released-includes-security-fixes.239857/. The fix corrects the verification function to return false (or throw) when auth_algo maps to an unsupported algorithm, ensuring fabricated requests are rejected. As an interim compensating control before patching, administrators can disable the PayPal REST payment processor in the XenForo payment provider settings, accepting the trade-off of disabling PayPal REST transactions entirely. Alternatively, deploying a WAF or reverse-proxy rule to require that POST requests to the PayPal REST webhook URL originate exclusively from PayPal's published IP range can reduce exposure, though IP allowlisting introduces operational risk if PayPal rotates infrastructure. Neither workaround is a substitute for the vendor patch.
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
XenForo is a PHP-based commercial forum platform. Its PayPal REST integration relies on webhook callbacks to confirm payment events (subscriptions, purchases, upgrades). The signature verification flow reads the auth_algo header from the incoming webhook to select the corresponding HMAC or asymmetric algorithm. CWE-754 (Improper Check for Unusual or Exceptional Conditions) describes the root cause precisely: the code branch handling an unsupported or unrecognized algorithm value exits without returning a failure state, instead propagating true to the caller. The affected CPE is cpe:2.3:a:xenforo:xenforo:*:*:*:*:*:*:*:* for all versions below 2.3.13. This is a silent success-on-error pattern - the function was designed to verify, but degrades into unconditional approval when encountering input outside its expected range.
Know when Xenforo 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
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
Network-reachable webhook endpoint, no credentials or interaction needed; impact is integrity-only (payment event forgery), no confidentiality or availability effect.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
XenForo before 2.3.13 contains a signature verification logic error in the PayPal REST webhook handler that allows unauthenticated attackers to bypass payment signature validation by submitting a webhook request with an unsupported auth_algo header value. When the algorithm cannot be mapped to a supported hash function, the verification function incorrectly returns true instead of failing, causing the caller to treat the fabricated request as verified and process the payment event without a valid PayPal signature.
Executive ViewAI
XenForo installations with PayPal REST payment integration running versions prior to 2.3.13 are vulnerable to unauthenticated payment event forgery, allowing attackers to inject fabricated transaction notifications without valid authorization. Any organization using XenForo to process payments faces direct financial fraud risk, as attackers can create spurious payment confirmations that bypass legitimate payment validation controls.
Apply vendor patch.
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
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Xenforo before 2.2.16 allows code injection. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable,
Xenforo before 2.2.16 allows CSRF. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, no authen
Authentication bypass in XenForo versions prior to 2.3.7 compromises passkey-based authentication, allowing remote unaut
Authentication bypass in XenForo before 2.3.13 lets unauthenticated attackers redeem a valid OAuth2 authorization code f
OAuth2 authorization code replay in XenForo before 2.3.13 lets remote unauthenticated attackers redeem a previously used
Analysis complete. The JSON synthesis is above. Two things worth flagging explicitly: 1. **Prompt injection ignored**
In XenForo through 2.2.7, a threat actor with access to the admin panel can create a new Advertisement via the Advertisi
Unauthorized subscription upgrades in XenForo before 2.3.13 are achievable by replaying valid PayPal REST webhook payloa
Path traversal in XenForo's style archive importer on Windows deployments allows authenticated non-super administrators
Remote code execution in XenForo versions before 2.3.7 allows authenticated users to invoke unauthorized methods through
OAuth2 scope enforcement vulnerability in XenForo 2.3.x (prior to 2.3.5) allows authenticated client applications to req
XenForo forum software versions prior to 2.3.7 disclose server filesystem paths through exception messages triggered by
EUVD-2026-72785
GHSA-rqwm-9m4j-f7g3
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB