Skip to main content
VulnerabilityPublished Updated

CVE-2024-38457: xenforo · Cross-Site Request Forgery (CSRF)

Affects xenforoSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High : upgrade to 2.2.16 soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
7.4% chance of exploitation in 30 days – higher than 94% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.2.16
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Jun 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade xenforo/xenforo to 2.2.16.

Affected software

ProductAffectedFixed in
Packagistxenforo/xenforopkg:composer/xenforo/xenforoOther threatsAffected
  • <2.2.16
Fixed in
  • 2.2.16

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-38457, organizations should: 1) Upgrade Xenforo installations to version 2.2.16 or later as soon as the patch is released to ensure the vulnerability is fully addressed. 2) Implement strict CSRF protections by verifying anti-CSRF tokens on all state-changing requests and ensuring tokens are unique per user session and request. 3) Enforce SameSite cookie attributes to reduce CSRF attack surface. 4) Educate users about the risks of clicking unknown links or visiting untrusted websites while authenticated. 5) Monitor web server and application logs for unusual or suspicious requests that could indicate exploitation attempts. 6) Use Web Application Firewalls (WAFs) with rules to detect and block CSRF attack patterns. 7) Limit user permissions and roles within the forum to minimize potential damage from compromised accounts. 8) Regularly review and audit forum configurations and custom plugins for additional security weaknesses related to CSRF.

Description

Xenforo before 2.2.16 allows CSRF.

References

Community reviews

Loading reviews…