Skip to main content

XenForo CVE-2026-73314

| EUVDEUVD-2026-72785 HIGH
Improper Check for Unusual or Exceptional Conditions (CWE-754)
2026-09-08 VulnCheck GHSA-rqwm-9m4j-f7g3
8.7
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

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

  1. Access
    Identify XenForo instance with PayPal REST enabled
  2. Delivery
    Craft webhook POST with unsupported auth_algo header
  3. Exploit
    Submit to webhook endpoint unauthenticated
  4. Execution
    Verification function returns true on algorithm mismatch
  5. Persist
    Fabricated payment event accepted as valid
  6. Impact
    Fraudulent 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 auth_algo header set to an arbitrary unsupported string (e.g., an invented algorithm name). The verification function fails to find a matching hash function, returns true, and XenForo processes the event as a legitimate PayPal notification - granting the attacker a paid membership or subscription upgrade without any actual payment. No public exploit code has been identified at time of analysis, but the logic is straightforward to reproduce from the public VulnCheck advisory.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.5% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – 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

Xenforo 0 <2.3.13

Affected Packages

euvd xenforo fix: 2.3.13

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

Vendor (VulnCheck) PRIMARY 8.7 HIGH
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
vuln.today AI 7.5 HIGH

Network-reachable webhook endpoint, no credentials or interaction needed; impact is integrity-only (payment event forgery), no confidentiality or availability effect.

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

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
High
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

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

Why It Matters

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.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.5%
Top 62% exploitable
Prevalence
Medium
popular niche forum platform, significant community operator footprint
Data Quality
6 sources
Confidence: High

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 HIGH
CISA KEV No
Public POC No
EPSS 0.5%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.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
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

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

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

CVE-2024-38458 HIGH POC
8.8 Jun 16

Xenforo before 2.2.16 allows code injection. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable,

CVE-2024-38457 HIGH POC
8.8 Jun 16

Xenforo before 2.2.16 allows CSRF. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, no authen

CVE-2025-71279 CRITICAL
9.3 Apr 01

Authentication bypass in XenForo versions prior to 2.3.7 compromises passkey-based authentication, allowing remote unaut

CVE-2026-73309 CRITICAL
9.1 Sep 08

Authentication bypass in XenForo before 2.3.13 lets unauthenticated attackers redeem a valid OAuth2 authorization code f

CVE-2026-73311 CRITICAL
9.1 Sep 08

OAuth2 authorization code replay in XenForo before 2.3.13 lets remote unauthenticated attackers redeem a previously used

CVE-2026-73312 CRITICAL
9.1 Sep 08

Analysis complete. The JSON synthesis is above. Two things worth flagging explicitly: 1. **Prompt injection ignored**

CVE-2021-43032 MEDIUM POC
4.8 Nov 03

In XenForo through 2.2.7, a threat actor with access to the admin panel can create a new Advertisement via the Advertisi

CVE-2026-73316 HIGH
8.7 Sep 08

Unauthorized subscription upgrades in XenForo before 2.3.13 are achievable by replaying valid PayPal REST webhook payloa

CVE-2026-74239 HIGH
8.6 Sep 08

Path traversal in XenForo's style archive importer on Windows deployments allows authenticated non-super administrators

CVE-2025-71281 HIGH
8.7 Apr 01

Remote code execution in XenForo versions before 2.3.7 allows authenticated users to invoke unauthorized methods through

CVE-2025-71278 HIGH
8.7 Apr 01

OAuth2 scope enforcement vulnerability in XenForo 2.3.x (prior to 2.3.5) allows authenticated client applications to req

CVE-2025-71282 HIGH
8.7 Apr 01

XenForo forum software versions prior to 2.3.7 disclose server filesystem paths through exception messages triggered by

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