Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconIdentify public PayPal REST webhook endpoint
-
DeliveryCraft POST request with malicious cert URL in webhook headers
-
ExploitXenForo server issues outbound HTTP fetch to attacker-controlled URL
-
InstallRedirect or target cloud metadata service (169.254.169.254)
-
C2Extract IAM role credentials from metadata response
-
ExecuteAuthenticate to cloud APIs with stolen credentials
-
ImpactPivot to cloud-attached storage and services
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Credential 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 only the ability to send an unauthenticated HTTP POST to the XenForo PayPal REST webhook endpoint, which is publicly internet-accessible on any XenForo installation with PayPal REST payment processing configured and active. If the PayPal REST payment integration is not configured or the webhook is not registered, the handler may not be reachable, significantly reducing exposure. The highest-impact exploitation path - IAM credential disclosure - additionally requires XenForo to be hosted on cloud infrastructure (AWS, GCP, Azure, or similar) with an accessible instance metadata service endpoint at 169.254.169.254; bare-metal or on-premises deployments retain SSRF risk but lose the credential-exfiltration impact chain. No authentication, session, or elevated privilege is required at any stage of the attack. |
| Impact | The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) confirms fully automated, unauthenticated, zero-complexity remote exploitation - the PayPal webhook endpoint is publicly accessible by design, removing all network-layer barriers. The impact is captured in SC:H (high confidentiality loss to a subsequent system), reflecting that the primary damage is exfiltration of cloud IAM credentials rather than data held directly on the XenForo host. The CVSS 4.0 score of 7.7 is consistent with this scoped-but-high secondary impact. EPSS data is not provided; however, the vulnerability class (SSRF to cloud metadata) is extremely well-understood by attackers, with abundant public tooling and demonstrated exploitation patterns against similar webhook handlers in other platforms. KEV status is not confirmed, and no public exploit exists at time of analysis. Real-world risk is highest for cloud-hosted XenForo deployments with PayPal REST enabled and permissive IAM roles; on-premises deployments face a reduced but non-zero risk (internal network pivoting remains possible). Defenders should not discount this due to the absence of a KEV listing - the attack is trivially constructible from the public VulnCheck advisory description. |
| Exploit ScenarioDerived | An attacker sends an unauthenticated HTTP POST to the XenForo PayPal webhook callback URL with the webhook certificate URL header set to http://169.254.169.254/latest/meta-data/iam/security-credentials/my-role. XenForo's webhook handler fetches that address and processes the response, returning the AWS temporary credentials (AccessKeyId, SecretAccessKey, Token) to the attacker via the server's response or a side-channel observable through timing. The attacker then uses those credentials to enumerate S3 buckets, RDS instances, or other cloud resources attached to the compromised role. No public exploit code exists, but the attack is trivially constructed from the public VulnCheck advisory. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 08, 2026
Server-Side Request Forgery in XenForo's PayPal REST webhook handler enables unauthenticated remote attackers to coerce the application server into making arbitrary outbound HTTP requests by supplying a crafted certificate URL in webhook request headers. All XenForo versions prior to 2.3.13 are affected due to the absence of scheme, hostname, or allowlist validation on the attacker-controlled URL. The primary exploitation path targets cloud-hosted deployments: the server can be directed to reach the AWS, GCP, or Azure instance metadata service (169.254.169.254), potentially exfiltrating IAM role credentials and enabling lateral movement into cloud infrastructure. No public exploit has been identified at time of analysis, but the attack surface - an unauthenticated POST to a publicly reachable webhook endpoint - makes this highly automatable against cloud-hosted XenForo instances.
RemediationAI
Upgrade XenForo to version 2.3.13 or later; this release introduces scheme, hostname, and allowlist validation for the PayPal webhook certificate URL parameter and is available from https://xenforo.com/community/threads/xenforo-2-3-13-and-add-ons-released-includes-security-fixes.239857/. For deployments that cannot patch immediately, the most impactful compensating control is to enforce IMDSv2 on AWS EC2 instances (or equivalent token-gated metadata access on GCP/Azure), which breaks the IAM-credential-exfiltration path since IMDSv2 requires a session-oriented PUT request that a simple SSRF fetch cannot produce. Additionally, configure host-level or WAF egress rules to block outbound HTTP/HTTPS from the web server process to 169.254.0.0/16 and all RFC-1918 ranges - this does not interfere with normal XenForo operations or legitimate PayPal traffic. As a last resort, disabling PayPal REST payment integration at the XenForo admin level removes the vulnerable endpoint entirely but interrupts payment processing. Audit existing IAM roles attached to the hosting instance for least-privilege compliance regardless of patch status.
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 (cpe:2.3:a:xenforo:xenforo:*) is a commercial PHP-based internet forum platform. Its PayPal REST payment integration includes a webhook handler that processes incoming POST callbacks from PayPal. As part of certificate-based webhook verification, the handler fetches a certificate from a URL supplied within the incoming request headers. CWE-918 (Server-Side Request Forgery) materialises here because the handler performs this outbound HTTP fetch without validating the URL's scheme, hostname, or comparing it against an allowlist of legitimate PayPal certificate endpoints. An attacker can substitute any URL - including RFC-1918 addresses, link-local addresses (169.254.169.254 for cloud metadata), or internal service hostnames - causing the XenForo PHP process to act as an unauthenticated proxy to otherwise inaccessible internal network resources.
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:N/VA:N/SC:H/SI:N/SA:N
Network-reachable unauthenticated endpoint, no complexity; scope changes to subsequent cloud systems with high confidentiality loss via IAM credentials; no integrity or availability impact.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
XenForo before 2.3.13 contains a server-side request forgery vulnerability in the PayPal REST webhook handler that allows unauthenticated attackers to cause the server to make outbound HTTP requests to arbitrary destinations by supplying a crafted certificate URL in webhook headers without scheme, hostname, or allowlist validation. Attackers can submit a crafted POST to the PayPal webhook callback endpoint to reach internal network resources including cloud instance metadata services, potentially disclosing IAM credentials or enabling secondary internal service exploitation.
Executive ViewAI
XenForo versions prior to 2.3.13 contain an unauthenticated vulnerability allowing attackers to steal cloud infrastructure credentials from AWS, GCP, and Azure metadata services. For organizations using cloud-hosted XenForo, this creates direct exposure to credential compromise and lateral movement into production infrastructure.
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
Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.
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
Unauthenticated payment event forgery in XenForo before 2.3.13 stems from a logic error in the PayPal REST webhook signa
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
EUVD-2026-72786
GHSA-x4fx-w4wf-c38c
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB