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

CVE-2025-28888

HIGH · 8.1 CVSS v3.1 Published 2025-06-09
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 GiftXtore bw-giftxtore allows PHP Local File Inclusion.This issue affects GiftXtore: from n/a through < 1.7.7.

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 vulnerability exists in the BZOTheme GiftXtore component (bw-giftxtore) versions prior to 1.7.7. The vulnerability allows attackers to include arbitrary PHP files from the server through improper validation of input parameters used in include/require statements.

MitigationUpgrade to GiftXtore version 1.7.7 or later. If upgrading is not immediately possible, implement input validation and whitelist-based file inclusion controls 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 the GiftXtore component installation
    Search the web server filesystem for directories named 'bw-giftxtore', 'giftxtore', or 'bzo-theme-giftxtore' typically found under the web root or application components folder
    Affected if The GiftXtore component directory exists on the server
  2. Determine the installed GiftXtore version
    Check the component version file (such as version.php, manifest.xml, or a CHANGELOG file within the GiftXtore directory) and compare the version number to 1.7.7
    Affected if The installed version is lower than 1.7.7 or the version cannot be determined (treat as vulnerable)
  3. Identify PHP files handling include/require statements
    Search the GiftXtore directory for PHP files containing include(), require(), include_once(), or require_once() functions that use variables or request parameters in the file path
    Affected if Files with dynamic file inclusion using unsanitized input parameters are present
  4. Inspect input validation in inclusion logic
    Examine the PHP files identified in step 3 to determine whether the parameters used in include/require statements are validated against a whitelist or sanitized to prevent path traversal
    Affected if Input parameters used in include/require statements are not validated or can be manipulated through user-supplied input (GET/POST parameters)
  5. Test for accessible vulnerable endpoints
    If the application exposes parameters that feed into the include/require logic (common parameter names include 'page', 'file', 'path', 'template', or 'action'), attempt to supply path traversal sequences such as '../' or absolute paths to confirm the vulnerability is reachable
    Affected if The application allows path traversal or arbitrary file inclusion through HTTP request parameters

The environment is affected if the BZOTheme GiftXtore component version is below 1.7.7 and the application exposes vulnerable file inclusion endpoints with insufficient input validation.

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 GiftXtore version 1.7.7 or later. If upgrading is not immediately possible, implement input validation and whitelist-based file inclusion controls to prevent path traversal attacks.

Recommended fix Moderate confidence

GiftXtore version 1.7.7 or later

  1. 1. Backup your entire WordPress installation, including the database, before proceeding with any updates.
  2. 2. Download the latest version of GiftXtore (version 1.7.7 or later) from the official BZOTheme source or WordPress repository.
  3. 3. If available through WordPress admin, navigate to Dashboard > Updates or Plugins > Installed Plugins and update GiftXtore to the latest version.
  4. 4. Alternatively, upload the new version via FTP/SFTP by replacing the bw-giftxtore plugin/theme files in wp-content/plugins/ or your theme directory.
  5. 5. Verify the update was successful by checking the plugin/theme version number.
  6. 6. Test critical site functionality to ensure the update did not break existing features.
  7. 7. Review your web server logs and the application for any signs of exploitation attempts.

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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