dbcve.org
XenforoApplication

CVE-2025-71282

HIGH · 7.5 CVSS v3.1 Published 2026-04-01
Fix available
A fix is available. Upgrade to 2.3.7 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 discloses filesystem paths through exception messages triggered by open_basedir restrictions. This allows an attacker to obtain information about the server's directory structure.

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 versions prior to 2.3.7 contain an information disclosure vulnerability where exception messages triggered by PHP's open_basedir restrictions expose absolute filesystem paths. An attacker can exploit this to map the server's directory structure by triggering specific error conditions.

MitigationUpgrade XenForo to version 2.3.7 or later, which contains the fix for this path disclosure issue.

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm XenForo installation
    Look for XenForo installation directories (commonly /home/user/public_html or similar web root paths). Check for the presence of src/XF.php or the admin.php entry point in your web directory.
    Affected if XenForo software is present on the server
  2. Identify XenForo version
    Access the XenForo admin control panel and navigate to the Dashboard or About section to view the installed version. Alternatively, check for a VERSION file in the XenForo installation root if accessible.
    Affected if Installed version is earlier than 2.3.7
  3. Check if PHP open_basedir is configured
    Create a PHP info page (phpinfo.php) with content '<?php phpinfo(); ?>' and access it via browser, then search for the 'open_basedir' directive. Or check your server PHP configuration (php.ini, .htaccess, or virtual host config) for open_basedir settings.
    Affected if open_basedir is set and restricts filesystem access (value is not empty or shows path restrictions)
  4. Test for path disclosure via error triggering
    Attempt to trigger the error condition by accessing XenForo features that interact with the filesystem (such as attachment uploads, template edits, or addon installations) while monitoring for error messages that may be displayed.
    Affected if Error messages display absolute server paths (such as /home/, /var/www/, or similar full filesystem paths) when operations are blocked by open_basedir

A server is affected if running XenForo version earlier than 2.3.7 with PHP open_basedir restrictions enabled, and absolute filesystem paths appear in error messages.

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 this path disclosure issue.

Recommended fix High confidence

XenForo 2.3.7

  1. Download XenForo 2.3.7 from the official XenForo customer area at xenforo.com
  2. Backup your existing XenForo installation and database before upgrading
  3. Upload the new XenForo 2.3.7 files to your server, replacing the existing installation
  4. Run the upgrade script or navigate to the admin panel to complete the upgrade process
  5. Verify that the upgrade was successful by checking the XenForo version in the admin control panel
  6. Test that exception messages no longer disclose filesystem paths by triggering scenarios that would previously expose open_basedir restriction errors
Caveat Review XenForo 2.3.7 release notes for any deprecated features or required database changes before upgrading

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-71282 — 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-71282 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