dbcve.org
XenforoApplication

CVE-2025-71281

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-01
Fix available
A fix is available. Upgrade to 2.3.7 or later.
See remediation →
100/100
Remediation priority · Urgent
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 does not properly restrict methods callable from within templates. A loose prefix match was used instead of a stricter first-word match for methods accessible through callbacks and variable method calls in templates, potentially allowing unauthorized method invocations.

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 2.3.7 contains a template injection vulnerability where method access controls use loose prefix matching instead of strict first-word matching. This allows attackers to invoke methods whose names start with allowed prefixes, potentially executing unauthorized operations through template callbacks.

MitigationUpgrade XenForo to version 2.3.7 or later to apply the stricter first-word method matching. If immediate patching is not possible, review template customization for suspicious callback usage.

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
High
Availability
High

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

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 version
    Locate the version file or admin panel. Check src/XF.php for the version constant, or log into the admin control panel and navigate to Setup > Options > Basic board information to view the installed version.
    Affected if The installed version is before 2.3.7 (e.g., 2.3.6, 2.3.0, 2.2.x, etc.)
  2. Verify template system is in use
    Check if custom templates exist in the installation. Look in the admin panel under Appearance > Templates, or check the src/XF/Template directory for custom template files.
    Affected if Custom templates or template modifications are present that utilize callback syntax (e.g., {{ $xf.templateVariable.method() }}) or variable method calls
  3. Confirm template callback functionality is enabled
    Review template files for callback syntax patterns like {{ callback('methodName') }} or dynamic method invocation such as {{ $var.$method() }}. Check the src/XF/Template/Compiler/Extension.php file if accessible to see if callback processing is active.
    Affected if Templates contain callable template methods or dynamic method invocation patterns that rely on loose prefix matching
  4. Check for exposed template variable access
    Examine template files to determine if user-controllable data can influence template variable names or method names. Look for templates that accept user input and pass it to template functions without sanitization.
    Affected if Templates accept external input (request parameters, user data) that could be used to influence method names called in template callbacks

You are affected if your XenForo installation is version 2.3.6 or earlier AND your templates utilize callback functionality or dynamic method calls that could invoke unintended methods through loose prefix matching.

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 to apply the stricter first-word method matching. If immediate patching is not possible, review template customization for suspicious callback usage.

Recommended fix High confidence

XenForo 2.3.7

  1. Backup your XenForo database and files before proceeding
  2. Download XenForo version 2.3.7 from the official XenForo members area or your customer account
  3. Upload the upgrade package to your server and extract it to your XenForo installation directory
  4. Run the upgrade script by accessing your forum URL (the system will automatically detect and apply the upgrade)
  5. Clear any caching systems (if used) such as Redis, Memcached, or file-based caches
  6. Verify the upgrade was successful by checking the admin control panel version information
  7. Test critical functionality to ensure the upgrade did not break existing features
Caveat Review XenForo 2.3.7 release notes for any template syntax changes or deprecated features that may affect custom styles or add-ons

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
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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