dbcve.org
XenforoApplication

CVE-2025-71280

MEDIUM · 5.5 CVSS v3.1 Published 2026-04-01
Fix available
A fix is available. Upgrade to 2.3.7 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
XenForo before 2.3.7 allows information disclosure via local account page caching on shared systems. On systems where multiple users share a browser or machine, cached account pages could expose sensitive user information to other local users.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

XenForo before version 2.3.7 contains a caching vulnerability on the local user account page. When multiple users share the same browser or machine, account pages with sensitive user information are cached without proper isolation, allowing subsequent local users to view the previous user's account data.

MitigationUpgrade XenForo to version 2.3.7 or later, which contains the fix for proper account page cache isolation on shared systems.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
XenforoApplication
Affected:< 2.3.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify XenForo installation directory
    Locate the XenForo installation on your server. Common paths include /var/www/html/, /home/user/public_html/, or your web root directory. Look for the src/addons/XenForo directory or a library/XenForo directory containing XenForo.php
    Affected if XenForo is not found in expected locations
  2. Determine installed XenForo version
    Open the file library/XenForo/Application.php (or src/Xf.php in newer installations) and locate the version constant near the top of the file, for example: const VERSION = '2.3.6'; or const VERSION = '2.3.7';
    Affected if The version number returned is less than 2.3.7
  3. Check admin panel version display
    Log into the XenForo admin control panel (admin.php) and navigate to Home > Dashboard or Tools > PHP Info. The XenForo version is displayed on the dashboard overview page
    Affected if Admin panel shows a version before 2.3.7
  4. Determine if environment has shared browser access
    Assess whether multiple users access XenForo from the same browser or machine. This includes: public terminal access, shared work stations, browser-based caching on multi-user systems, or proxy servers serving multiple users
    Affected if Multiple users share the same browser instance, machine, or are behind a shared caching proxy

You are affected if your XenForo installation version is before 2.3.7 AND multiple users access the system from shared browsers or machines where browser caching could expose one user's account page to subsequent users on that same browser.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.3.7 or later
Fixed in 2.3.7
Interim mitigation

Upgrade XenForo to version 2.3.7 or later, which contains the fix for proper account page cache isolation on shared systems.

Recommended fix Moderate confidence

XenForo 2.3.7

  1. 1. Backup your XenForo database and files before proceeding with any upgrade.
  2. 2. Download XenForo 2.3.7 from the official XenForo customer area at xenforo.com or your licensed download area.
  3. 3. Upload the new XenForo 2.3.7 files to your server, overwriting the existing installation.
  4. 4. Run the XenForo upgrade script by accessing your forum URL (the system will automatically detect and prompt for upgrade if needed).
  5. 5. Clear all caches through the XenForo admin control panel (Tools > Cache > Clear Cache).
  6. 6. Clear your browser cache and test that account pages load correctly for multiple user accounts.
  7. 7. Verify that sensitive information is no longer exposed between shared users on the same system.
Caveat Review XenForo 2.3.7 release notes for any template changes or add-on compatibility issues before upgrading production systems

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Xenforo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-71280 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-71280 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data