/

CVE-2026-73315

Severity:

HIGH RISK

(8.6)

SSRF (CWE-918) in XenForo PayPal Webhook Handler Endpoint

CVE-2026-73315

Analyzed

Vulnerability type

Category:

Server-Side Request Forgery

CWE:

CWE-918

Impact:

Unauthorized server-side network requests and potential internal service or credential exposure

Severity:

HIGH RISK

(8.6)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A server-side request forgery vulnerability in XenForo's PayPal REST webhook handler allows unauthenticated attackers to make the server send HTTP requests to attacker-selected destinations. The risk is greatest when the server can reach internal services, including cloud metadata endpoints, because responses or follow-on access may expose sensitive credentials or enable further attacks.

Affected context

The vulnerability occurs in XenForo deployments that expose the PayPal REST webhook callback and process a certificate URL supplied through webhook headers. Risk depends on whether the handler accepts URLs without validating their scheme, hostname, destination, and membership in an approved allowlist, and whether the hosting environment can reach internal network services or cloud metadata endpoints.

Exploit preconditions

  • Attack surface: The PayPal REST webhook callback endpoint
  • Required access: Network access to submit a webhook request; authentication may not be required
  • Trigger point: Processing of a crafted certificate URL in webhook headers
  • Why exploitation is possible: The handler may initiate outbound HTTP requests before enforcing scheme, hostname, destination, or allowlist restrictions
  • Environmental factor: Impact increases when the XenForo server can access internal services, metadata endpoints, or privileged network segments

Why this happens

The underlying bug is insufficient validation of a server-controlled outbound request target. A user-influenced certificate URL is treated as a trusted destination without strict parsing and authorization of its scheme, hostname, resolved address, and redirect behavior. This maps to CWE-918: Server-Side Request Forgery, where an attacker can influence a server into making requests to unintended network locations.

Potential impact

  • The server may send HTTP requests to internal or otherwise restricted destinations
  • Cloud instance metadata may disclose temporary IAM or service credentials
  • Internal services may be probed or contacted from a trusted network position
  • Attackers could exploit reachable internal services as a secondary step
  • Sensitive response data may be exposed through application behavior or logs

General mitigation guidance

Mitigation generally focuses on reducing trust in user-supplied URLs and enforcing a narrowly defined outbound request policy.

Common defensive patterns include:

  • Permit only explicitly required URL schemes and approved hostnames
  • Resolve and validate destinations before connecting, including protection against private, loopback, link-local, and otherwise restricted address ranges
  • Revalidate destinations after DNS resolution and across redirects
  • Prefer fixed, server-configured certificate endpoints over URLs supplied by webhook requests
  • Restrict outbound network access from the application using egress controls
  • Apply least-privilege identity permissions and limit access to cloud metadata services
  • Avoid returning fetched content or detailed network errors to untrusted callers

How teams detect issues like this

Organizations can detect SSRF risks through:

  • Static analysis rules for HTTP clients receiving URLs from request headers, parameters, or bodies
  • Code review checks for missing scheme, hostname, redirect, DNS, and private-address validation
  • Runtime monitoring of unusual outbound requests from the webhook process
  • Egress policy alerts for connections to metadata services, loopback addresses, private ranges, or unexpected domains
  • Policy enforcement requiring approved destination lists for server-initiated HTTP requests
  • Automated security review tools that identify user-controlled URL flows into network clients

Sources

SourceLink
bombobombone.github.iobombobombone.github.io/posts/cve-2026-73315/
github.comgithub.com/BomboBombone/CVE-2026-73315
vulncheck.comvulncheck.com/advisories/xenforo-ssrf-via-paypal-rest-webhook-handler
xenforo.comxenforo.com/community/threads/security-fixes-released-for-all-xenforo-and-media-gallery-versions-2-2-0-2-3-12.239856/
xenforo.comxenforo.com/community/threads/xenforo-2-3-13-and-add-ons-released-includes-security-fixes.239857/

Frequently asked

questions

It may be remotely exploitable when the PayPal webhook callback is reachable by an attacker and accepts unauthenticated requests. Exploitability also depends on outbound network connectivity and the handler's processing behavior.

The described issue does not require an authenticated XenForo account. An attacker generally needs network access to the webhook endpoint and the ability to submit headers containing a crafted certificate URL.

Use fixed or tightly allowlisted certificate destinations, validate URL schemes and hostnames, block restricted address ranges, and control redirects and DNS resolution before making outbound requests.

Treat all externally supplied URLs as untrusted, enforce centralized outbound-request policies, monitor egress traffic, and limit application and cloud identities so that an SSRF event cannot readily access sensitive services or credentials.

Find out what's already
exploitable in your codebase.