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

CVE-2025-46230

HIGH · 7.5 CVSS v3.1 Published 2025-04-24
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 GhozyLab Popup Builder easy-notify-lite allows PHP Local File Inclusion.This issue affects Popup Builder: from n/a through <= 1.1.35.

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 easy-notify-lite WordPress plugin by GhozyLab contains a PHP Local File Inclusion (LFI) vulnerability due to improper control of filenames in include/require statements. An attacker could potentially exploit this to include arbitrary local PHP files, which may lead to remote code execution depending on file contents and server configuration.

MitigationUpdate to the latest patched version of the easy-notify-lite plugin. If no patch is available, disable the plugin. Apply proper input validation and path sanitization to prevent directory traversal in file inclusion operations.

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. Verify easy-notify-lite plugin is installed
    Navigate to WordPress admin dashboard > Plugins and look for 'easy-notify-lite' by GhozyLab, or check the /wp-content/plugins/ directory for the easy-notify-lite folder
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > easy-notify-lite and note the version number displayed, or check the main plugin PHP file for the 'Version' header comment
    Affected if The version matches any known affected version range for this CVE
  3. Locate the vulnerable file inclusion code
    Search the plugin files for include/require statements that use unsanitized variables in the path (e.g., include($_GET['file']), include($_REQUEST['path']), or similar dynamic file inclusion patterns)
    Affected if Dynamic file inclusion using user-controlled input without proper sanitization is found
  4. Check for directory traversal vulnerability
    Test the suspected parameter with path traversal sequences (e.g., ../../wp-config.php) to see if the application allows accessing files outside the intended directory
    Affected if The application permits directory traversal in file inclusion parameters
  5. Verify PHP configuration
    Check php.ini for allow_url_include=1 (for RFI) and review the web server error logs for any LFI exploitation attempts
    Affected if PHP configuration allows dangerous file operations and the vulnerable code path is accessible via web request
  6. Check for signs of exploitation
    Review web server access logs for unusual include/require requests with traversal patterns (e.g., ../../), and examine the plugin directory for any unexpected PHP files
    Affected if Log evidence shows traversal attempts or unexpected files exist in the plugin directory

A user is affected if the easy-notify-lite plugin is installed, the installed version falls within the affected range, and the vulnerable file inclusion code with unsanitized input is present and accessible.

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 to the latest patched version of the easy-notify-lite plugin. If no patch is available, disable the plugin. Apply proper input validation and path sanitization to prevent directory traversal in file inclusion operations.

Recommended fix Moderate confidence

Latest version of easy-notify-lite plugin (verify on WordPress plugin repository or vendor site for version higher than 1.1.35)

  1. 1. Navigate to the WordPress admin dashboard and locate the easy-notify-lite plugin under Plugins.
  2. 2. Check if an update is available for the easy-notify-lite plugin.
  3. 3. If an update is available, update the plugin to the latest version that addresses the Local File Inclusion vulnerability.
  4. 4. Verify the plugin has been updated successfully.
  5. 5. Test the notify functionality to ensure the plugin still works correctly after the update.
  6. 6. Consider implementing additional web application firewall (WAF) rules as a temporary mitigation until the plugin can be updated.

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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