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

CVE-2025-26985

HIGH · 8.1 CVSS v3.1 Published 2025-02-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Majestic Support Majestic Support majestic-support allows PHP Local File Inclusion.This issue affects Majestic Support: from n/a through <= 1.0.6.

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

A PHP Local File Inclusion (LFI) vulnerability exists in Majestic Support versions up to 1.0.6 where user-supplied input is used in include/require statements without proper validation. This allows attackers to potentially read sensitive local files from the server filesystem by manipulating the file path parameters.

MitigationImplement strict input validation using whitelist approaches for file inclusions, utilize basename() and realpath() functions to sanitize paths, and refactor code to avoid dynamic include/require statements with user input.

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

CVSS:3.1/AV:N/AC:H/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 Majestic Support version
    Locate the version file or header in the Majestic Support installation - typically found in a version.php file, admin configuration panel, or the main index.php header comment. Compare the version number to the affected range (any version up to and including 1.0.6).
    Affected if The installed version is 1.0.6 or lower, or if no version can be determined but the product is confirmed as Majestic Support.
  2. Locate PHP files with dynamic includes
    Search the Majestic Support source code for patterns where user-supplied parameters (such as $_GET, $_POST, or $_REQUEST) are used within include(), require(), include_once(), or require_once() statements without proper sanitization.
    Affected if Files containing include/require statements that directly incorporate request parameters without validation are found.
  3. Identify vulnerable parameters
    Examine the identified include/require code for parameters that accept file paths (commonly named 'file', 'page', 'path', 'template', 'load', or similar). Determine if these parameters can be controlled by external user input.
    Affected if The file path parameters are directly used in include/require statements and can be influenced by user input without sanitization functions like basename() or realpath().
  4. Verify path traversal capability
    Test or inspect whether the vulnerable parameter accepts relative paths (such as ../../../etc/passwd) or wrapper protocols (such as php://filter). Check if the application restricts file inclusions to a specific directory.
    Affected if The application allows path traversal sequences or does not restrict which files can be included, enabling reading of arbitrary local files.
  5. Check web server exposure
    Determine if the Majestic Support application is directly accessible via web browser and whether the vulnerable endpoints are reachable without authentication.
    Affected if The vulnerable file inclusion code is accessible over HTTP/HTTPS without requiring authentication or special privileges.

If Majestic Support version 1.0.6 or lower is installed and the application exposes PHP files that use user input in include/require statements without validation, the environment is affected by CVE-2025-26985.

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 input validation using whitelist approaches for file inclusions, utilize basename() and realpath() functions to sanitize paths, and refactor code to avoid dynamic include/require statements with user input.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation10.0 h
  • Testing6.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,220
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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