dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2026-49954

HIGH · 7.2 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/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
Discuz! X5.0 releases 20260320 through 20260610 contain a local file inclusion vulnerability that allows authenticated administrators to execute arbitrary code by importing a specially crafted plugin configuration containing path traversal sequences in the directory attribute. Attackers can trigger an exception during plugin installation to bypass sanitization routines, causing malicious paths to be stored unsanitized and subsequently passed to include(), which combined with file upload functionality escalates to arbitrary code execution in the context of the web server user.

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 · moderate confidence

Discuz! X5.0 suffers from a local file inclusion vulnerability in its plugin configuration import functionality. An authenticated administrator can import a malicious plugin configuration containing path traversal sequences (e.g., ../../) in the directory attribute. When an exception occurs during plugin installation, the sanitization routine is bypassed, allowing the crafted path to be stored unsanitized. This path is later passed to PHP's include() function, and when combined with the file upload functionality, enables arbitrary code execution as the web server user.

MitigationImplement strict whitelist-based path validation that cannot be bypassed by exceptions, ensure sanitization always runs regardless of error conditions, and restrict include() calls to a predefined safe directory whitelist.

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

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

CVSS:3.1/AV:N/AC:L/PR:H/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. Confirm Discuz! X5.0 installation
    Identify the Discuz! version by checking typical installation paths or admin panels for the version string 'X5.0' or 'Discuz! X Series version 5.0'
    Affected if The installed version is Discuz! X5.0 or falls within the X5.0 series range
  2. Verify administrator access
    Check if you have administrator-level credentials or session access to the Discuz! admin control panel
    Affected if You can authenticate as an administrator user with privileges to access plugin management functions
  3. Locate plugin import functionality
    Search for plugin configuration import features in the admin panel, typically under 'Plugin' or 'Extensions' management sections, or examine source code for 'import' or 'install' functions related to plugins
    Affected if The plugin import feature exists and is accessible to authenticated administrators
  4. Inspect plugin configuration handling code
    Examine the plugin installation code path, specifically looking for include() or require() calls that use user-supplied directory attributes without strict validation, and check if exception handlers can bypass sanitization logic
    Affected if The code passes directory path parameters from imported plugin configurations directly to include() without comprehensive validation that survives exception conditions
  5. Check file upload capability
    Verify whether file upload functionality is enabled in the plugin installation process or general settings, as this is required in combination with the LFI for remote code execution
    Affected if File uploads are permitted and can be combined with the include() vulnerability

You are affected if Discuz! X5.0 is installed, you have administrator access, and the plugin import feature passes unsanitized directory paths to PHP's include() function when exceptions occur during installation.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict whitelist-based path validation that cannot be bypassed by exceptions, ensure sanitization always runs regardless of error conditions, and restrict include() calls to a predefined safe directory whitelist.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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