dbcve.org
XenforoApplication

CVE-2024-25006

HIGH · 8.1 CVSS v3.1 Published 2024-02-29
Fix available
A fix is available. Upgrade to 2.2.14 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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.2.14 allows Directory Traversal (with write access) by an authenticated user who has permissions to administer styles, and uses a ZIP archive for Styles Import.

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.2.14 contains a directory traversal vulnerability in the Styles Import functionality. An authenticated user with permissions to administer styles can craft a malicious ZIP archive containing file paths with traversal sequences (e.g., ../../../) to write files to arbitrary locations on the server filesystem outside the intended styles directory.

MitigationUpgrade XenForo to version 2.2.14 or later. As an interim measure, restrict style administration permissions to only highly trusted administrators and review existing style imports for suspicious content.

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.2.14

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Check XenForo version
    Navigate to the XenForo admin control panel, then go to Options > Basic Board Information, or inspect the file src/addons/XenForo/Setup/Version.php or the version info displayed in the admin footer
    Affected if The installed version is lower than 2.2.14
  2. Identify users with Style administration permissions
    In the admin control panel, go to Users > Permissions > User Groups or Users > Administrators and review which users or groups have the 'style' or 'styleAdmin' permission enabled
    Affected if Any user account other than the primary administrator has style administration permissions
  3. Review recent style imports
    In the admin control panel, go to Appearance > Styles and examine the import history. Check for any styles imported from ZIP files that were not sourced from the official XenForo resource library
    Affected if Styles were imported from untrusted or third-party ZIP archives
  4. Inspect imported style files for traversal sequences
    If style imports exist, examine the ZIP files in the internal_data directory or extracted style directories for file paths containing ../ sequences. Check files like template.xml or less templates for anomalous path references
    Affected if Any style files contain directory traversal sequences like ../ in file paths
  5. Check server filesystem for unexpected files
    Review the XenForo root directory and parent directories for newly created files that do not belong to the XenForo installation, particularly PHP files or configuration files that may have been written via the traversal vulnerability
    Affected if Unexpected files exist outside the intended styles directory structure

You are affected if your XenForo installation is version 2.2.13 or earlier AND any user with style administration permissions imported a ZIP file from an untrusted source.

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.2.14 or later
Fixed in 2.2.14
Interim mitigation

Upgrade XenForo to version 2.2.14 or later. As an interim measure, restrict style administration permissions to only highly trusted administrators and review existing style imports for suspicious content.

Recommended fix High confidence

XenForo 2.2.14

  1. Create a complete backup of your XenForo database and all files
  2. Download XenForo version 2.2.14 or later from the official XenForo members area
  3. Upload the new XenForo 2.2.14 files to your server, overwriting the existing installation
  4. Run the upgrade by visiting your forum URL (the system will automatically apply any necessary database updates)
  5. Clear all caches via the XenForo admin control panel under Tools > Cache
  6. Verify the upgrade was successful by checking the version number in the admin control panel
Caveat Minor version upgrades typically have minimal breaking changes, but always test on a staging environment first and maintain backups

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

Fix this in Xenforo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-25006 — 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-2024-25006 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