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

CVE-2025-26894

HIGH · 7.5 CVSS v3.1 Published 2025-04-15
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 Mobeen Abdullah Coming Soon, Maintenance Mode site-mode allows PHP Local File Inclusion.This issue affects Coming Soon, Maintenance Mode: from n/a through <= 1.1.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

This is a PHP Local File Inclusion (LFI) vulnerability in the 'Coming Soon, Maintenance Mode' WordPress plugin by Mobeen Abdullah. The vulnerability allows remote attackers to manipulate file inclusion parameters to execute arbitrary PHP code or read sensitive files from the server filesystem, potentially leading to remote code execution.

MitigationUpdate the plugin to the latest available version; if no patch exists, disable and remove the plugin immediately and implement WAF 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
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. Identify the plugin installation
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and locate 'Coming Soon, Maintenance Mode' by Mobeen Abdullah. Note the installed version number displayed next to the plugin name.
    Affected if The plugin is installed and the version is lower than the fixed version (if known) or unpatched.
  2. Verify the plugin is active
    Check if the 'Coming Soon, Maintenance Mode' plugin is currently activated. In WordPress admin, go to Plugins and confirm the plugin shows 'Active' status.
    Affected if The plugin is active and a vulnerable version, making it exploitable.
  3. Inspect plugin PHP files for file inclusion functions
    Using file manager or SSH, navigate to wp-content/plugins/coming-soon-maintenance-mode (or similar path) and search PHP files for inclusion functions like include, require, include_once, or require_once that use unsanitized variables (e.g., $_GET, $_POST) in their path parameters.
    Affected if The plugin code contains file inclusion functions using user-supplied input without proper sanitization.
  4. Check for directory traversal patterns in access logs
    Review web server access logs (typically in /var/log/apache2/ or /var/log/nginx/) for requests to the plugin that contain '../' patterns or direct file paths in query parameters, which may indicate exploitation attempts.
    Affected if Suspicious directory traversal patterns are found in logs targeting this plugin.
  5. Review plugin configuration for enabled maintenance mode
    Check the plugin settings via WordPress admin or by inspecting the database wp_options table for option_name containing 'coming_soon' or 'maintenance_mode' to see if the feature is actively serving pages.
    Affected if The maintenance mode feature is enabled and the vulnerable code path is reachable.

A user is affected if the 'Coming Soon, Maintenance Mode' plugin by Mobeen Abdullah is installed, active, and running a version with unpatched file inclusion logic that allows user-controlled input to specify file paths.

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 the plugin to the latest available version; if no patch exists, disable and remove the plugin immediately and implement WAF rules to block directory traversal patterns (e.g., ../) in request parameters.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,620
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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