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

CVE-2025-28946

HIGH · 8.1 CVSS v3.1 Published 2025-06-27
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 BZOTheme PrintXtore bw-printxtore allows PHP Local File Inclusion.This issue affects PrintXtore: from n/a through < 1.7.8.

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 Local File Inclusion (LFI) vulnerability in BZOTheme PrintXtore bw-printxtore allows attackers to manipulate filename parameters in PHP include/require statements to load arbitrary files from the server. This can lead to sensitive file disclosure and potentially remote code execution. The vulnerability affects all versions prior to 1.7.8.

MitigationUpgrade to PrintXtore version 1.7.8 or later. If patching is not immediately possible, implement strict input validation and whitelist-based file inclusion logic to prevent path traversal attacks.

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. Locate PrintXtore installation
    Search the web server document root for directories named 'printxtore', 'bw-printxtore', or 'PrintXtore'. Common paths include /var/www/html/, /home/*/public_html/, or C:\inetpub\wwwroot\. Look for a folder containing files like index.php, config.php, or theme-specific PHP files.
    Affected if The PrintXtore software is present on the system.
  2. Identify installed version
    Open version.php, version.txt, or index.php within the PrintXtore directory and search for a variable like $version, VERSION, or a version string (e.g., '1.7.7'). If no explicit version file exists, check the header comments of core PHP files for a version number.
    Affected if The discovered version is lower than 1.7.8 (e.g., 1.7.7, 1.7.6, 1.5.0, etc.).
  3. Find vulnerable include/require patterns
    Within the PrintXtore directory, use grep or a file search to locate PHP files containing 'include(', 'require(', 'include_once(', or 'require_once(' where the included path uses a variable that could be user-controlled (e.g., include($filename), include($_GET['file']), require($path . 'file.php').
    Affected if User-controllable parameters are used in include/require statements without sanitization.
  4. Verify parameter exposure
    Examine the identified vulnerable PHP files to determine if the problematic parameter originates from GET, POST, or COOKIE superglobals. Test by attempting a controlled request (e.g., ?filename=../../config.php) against the affected endpoint, observing whether the server returns file contents.
    Affected if The parameter is directly passed from user input to include/require and the endpoint is accessible via HTTP.

A user is affected if PrintXtore is installed, the version is below 1.7.8, and the application exposes a filename parameter in include/require statements that can be manipulated through HTTP requests to traverse and load arbitrary server 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to PrintXtore version 1.7.8 or later. If patching is not immediately possible, implement strict input validation and whitelist-based file inclusion logic to prevent path traversal attacks.

Recommended fix Moderate confidence

1.7.8

  1. Backup the current PrintXtore installation and database before proceeding with the upgrade.
  2. Download PrintXtore version 1.7.8 or later from the official vendor source.
  3. Replace the existing PrintXtore files with the updated version 1.7.8 files.
  4. Verify that the include/require statements in the affected code no longer accept user-supplied input without proper validation.
  5. Test the application functionality to ensure the upgrade does not break existing features.
  6. Monitor application logs for any errors or unusual activity following the upgrade.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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