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

CVE-2025-28916

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Rashid Docpro docpro allows PHP Local File Inclusion.This issue affects Docpro: from n/a through <= 2.0.1.

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

Docpro versions up to 2.0.1 contain a PHP Local File Inclusion (LFI) vulnerability where user-controlled input is improperly used in include/require statements without proper validation. An attacker can exploit this to read sensitive local files or potentially achieve remote code execution depending on server configuration.

MitigationImplement strict input validation using whitelist approaches, basename(), and realpath() to sanitize file path parameters before use in include/require statements. Disable allow_url_include and consider web application firewall deployment as defense-in-depth.

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
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. Locate Docpro installation and version
    Search the web server document root for 'docpro' folders or check application metadata files (README, version.php, composer.json) for version information. Compare the found version against 'up to 2.0.1'.
    Affected if Docpro version 2.0.1 or lower is installed, or version cannot be determined but the application is present.
  2. Identify include/require statements using user input
    Search PHP source files for include, require, include_once, or require_once statements that reference variables (e.g., include($_GET['page'], include($page), include($_REQUEST['file']). Look for patterns where URL parameters appear to control the included file path.
    Affected if Any include/require statement uses raw user input (GET, POST, REQUEST, COOKIE) without sanitization is present in the codebase.
  3. Verify lack of input validation on file path parameters
    Review the code surrounding vulnerable include/require statements. Check if basename(), realpath(), or whitelist validation is applied to the input before inclusion. If none of these safeguards exist, the vulnerability is present.
    Affected if No basename(), realpath(), or whitelist validation is applied to user-supplied file path parameters before they are used in include/require.
  4. Check PHP configuration for allow_url_include
    Review php.ini or run 'php -i' to check the value of allow_url_include setting. Also check for any .htaccess or other PHP configuration that might affect this.
    Affected if allow_url_include is enabled (set to On), which would allow remote file inclusion in addition to local file inclusion.
  5. Test LFI exploitability with safe probe
    If the application accepts a parameter that controls file inclusion, attempt to include a known local file such as '/etc/passwd' (Linux) or 'C:\Windows\win.ini' (Windows) using the affected parameter. Observe if file contents are returned in the response.
    Affected if The application returns contents of arbitrary local files when a path traversal pattern (e.g., ../../) is provided in the vulnerable parameter.

A user is affected if Docpro version 2.0.1 or lower is running AND the codebase contains include/require statements using unsanitized user input that allow reading local files.

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, basename(), and realpath() to sanitize file path parameters before use in include/require statements. Disable allow_url_include and consider web application firewall deployment as defense-in-depth.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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