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

CVE-2025-26932

HIGH · 7.5 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 →
81/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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in QuantumCloud ChatBot chatbot allows PHP Local File Inclusion.This issue affects ChatBot: from n/a through <= 6.3.5.

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

PHP Local File Inclusion (LFI) vulnerability in QuantumCloud ChatBot plugin version 6.3.5 and earlier allows attackers to read sensitive local files on the server due to improper control of filenames in include/require statements. The vulnerability stems from insufficient input validation on parameters used in file inclusion functions.

MitigationUpgrade ChatBot to the latest version immediately. If no patch is available, disable the plugin. Implement strict whitelist-based input validation on all file inclusion parameters and disable allow_url_include in PHP configuration.

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

CVSS:3.1/AV:N/AC:H/PR:L/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 installed ChatBot plugin version
    Access the WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate the ChatBot plugin by QuantumCloud, and note the installed version number. Alternatively, check the plugin header comments in the main plugin file (typically /wp-content/plugins/chatbot/*.php) for the Version field.
    Affected if The installed version is 6.3.5 or any earlier version number.
  2. Verify plugin is active
    In WordPress admin, confirm the ChatBot plugin status shows as 'Active'. An inactive plugin with the vulnerability present still represents risk if activated.
    Affected if The plugin is currently activated on the WordPress site.
  3. Inspect plugin file structure for inclusion functions
    Examine PHP files in the ChatBot plugin directory (typically /wp-content/plugins/chatbot/) for dynamic include(), require(), include_once(), or require_once() statements that use variables or request parameters without sanitization. Search for patterns like 'include($_REQUEST[', 'require($', or similar unsanitized input in file inclusion functions.
    Affected if Dynamic file inclusion using unsanitized user input (GET/POST parameters) is found in the plugin code.
  4. Check PHP configuration for dangerous settings
    Review php.ini or check PHP configuration via phpinfo() for allow_url_include = On (enables remote file inclusion) and ensure open_basedir restrictions are properly configured to limit accessible directories.
    Affected if allow_url_include is enabled (though primarily relevant for RFI, it indicates a permissive PHP configuration) and no open_basedir restrictions exist.
  5. Audit access logs for suspicious file inclusion patterns
    Review web server access logs (Apache error.log, access.log, or Nginx access.log) for unusual requests to the ChatBot plugin endpoints. Look for patterns like '?file=../../etc/passwd' or similar path traversal attempts targeting the chatbot plugin files.
    Affected if Log evidence shows exploitation attempts or successful unauthorized file reads via the ChatBot plugin.

A user is affected if the ChatBot plugin version is 6.3.5 or earlier AND the plugin is active, with vulnerable file inclusion code present that accepts unsanitized input.

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

Upgrade ChatBot to the latest version immediately. If no patch is available, disable the plugin. Implement strict whitelist-based input validation on all file inclusion parameters and disable allow_url_include in PHP configuration.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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