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

CVE-2025-26957

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 Deetronix Affiliate Coupons affiliate-coupons allows PHP Local File Inclusion.This issue affects Affiliate Coupons: from n/a through <= 1.7.3.

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 · moderate confidence

The Deetronix Affiliate Coupons WordPress plugin versions through 1.7.3 contains a PHP Local File Inclusion (LFI) vulnerability due to improper control of filename in include/require statements. Attackers can potentially include arbitrary local files from the server, leading to sensitive data exposure (like configuration files containing database credentials) or remote code execution if they can upload malicious PHP files.

MitigationUpdate to the latest version of the Affiliate Coupons plugin immediately. If no patched version exists, disable the plugin and implement web application firewall rules to block directory traversal patterns (e.g., ../) in request parameters.

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. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Affiliate Coupons. The version number is displayed below the plugin name. Alternatively, check the plugin header in wp-content/plugins/affiliate-coupons/affiliate-coupons.php for 'Version:' comment.
    Affected if Version is 1.7.3 or any earlier version (the vulnerability affects through 1.7.3)
  2. Identify vulnerable include/require statements
    Search the plugin files (particularly in the /include/ directory if present) for include(), require(), include_once(), or require_once() statements that use variables or request parameters without proper sanitization. Look for patterns like 'include($_GET["file"])' or 'require($some_variable)'.
    Affected if Code contains include/require statements using unsanitized user input for file paths
  3. Locate the specific vulnerable endpoint
    Examine PHP files in the plugin for parameters used in file inclusion (commonly named 'page', 'file', 'template', 'view', 'path', or 'slug'). Test accessing these files directly via HTTP if the plugin is accessible without authentication.
    Affected if Plugin exposes an endpoint that accepts file path parameters without validation
  4. Verify directory traversal is possible
    If a vulnerable parameter is found, attempt a test request with a path like '../' to see if the server accepts traversal sequences. For example: yoursite.com/wp-content/plugins/affiliate-coupons/[vulnerable-file]?file=../../../../wp-config.php
    Affected if Server returns content of files outside the plugin directory when using ../ sequences
  5. Check for writable upload directories
    Review if the plugin allows file uploads and stores them in a web-accessible location. Look for upload functionality in the plugin code and check the /uploads/ directory for any files uploaded by the plugin.
    Affected if Plugin allows file uploads to a web-accessible directory, which could enable RCE via LFI

You are affected if you have Affiliate Coupons plugin version 1.7.3 or earlier installed and the plugin exposes an include/require statement using unsanitized user-supplied file paths that accepts directory traversal sequences.

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

Update to the latest version of the Affiliate Coupons plugin immediately. If no patched version exists, disable the plugin and implement web application firewall rules to block directory traversal patterns (e.g., ../) in request parameters.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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