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

CVE-2025-31015

HIGH · 7.5 CVSS v3.1 Published 2025-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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 Adrian Tobey WordPress SMTP Service, Email Delivery Solved! — MailHawk mailhawk allows PHP Local File Inclusion.This issue affects WordPress SMTP Service, Email Delivery Solved! — MailHawk: from n/a through <= 1.3.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 · moderate confidence

PHP Local File Inclusion vulnerability in MailHawk plugin <= 1.3.1 allows attackers to include arbitrary PHP files from the server filesystem due to improper control of filename parameters in include/require statements. This can lead to remote code execution if an attacker can control which files are included.

MitigationUpdate MailHawk plugin to latest version beyond 1.3.1. If no patch available, disable the plugin until fixed. Review and sanitize any file inclusion logic that uses user-controlled input.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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. Confirm MailHawk plugin is installed
    Navigate to WordPress admin dashboard > Plugins, or inspect the /wp-content/plugins/mailhawk/ directory via file system
    Affected if MailHawk plugin is present in the plugins directory
  2. Identify installed MailHawk version
    Check the plugin header in mailhawk.php main file for 'Version:' value, or view in WordPress Plugins > Installed Plugins list
    Affected if Version number is 1.3.1 or lower
  3. Locate file inclusion code in the plugin
    Search plugin source files for include, require, include_once, or require_once statements that use variables derived from $_GET, $_POST, or $_REQUEST parameters without sanitization
    Affected if Any include/require statement uses unsanitized user input in the file path
  4. Verify vulnerable endpoint accessibility
    Test accessing plugin pages or AJAX endpoints that accept file path parameters, checking if they can be manipulated to include arbitrary files
    Affected if The plugin exposes functionality that passes user-controlled parameters to file inclusion functions

If MailHawk plugin version is 1.3.1 or lower AND the plugin contains file inclusion code using unsanitized user input that is accessible via web requests, the environment is affected by CVE-2025-31015.

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

Update MailHawk plugin to latest version beyond 1.3.1. If no patch available, disable the plugin until fixed. Review and sanitize any file inclusion logic that uses user-controlled input.

Recommended fix Moderate confidence

Latest version of MailHawk (WordPress plugin) higher than 1.3.1

  1. 1. Log in to the WordPress admin dashboard.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate the MailHawk plugin (WordPress SMTP Service, Email Delivery Solved! — MailHawk).
  4. 4. If an update is available, click 'Update Now' to update to the latest patched version.
  5. 5. If no update is shown, manually download the latest version of MailHawk from the WordPress plugin repository and reinstall.
  6. 6. Verify the plugin is running a version higher than 1.3.1 after updating.

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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