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

CVE-2025-58973

HIGH · 7.5 CVSS v3.1 Published 2025-09-22
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 hashthemes Easy Elementor Addons easy-elementor-addons allows PHP Local File Inclusion.This issue affects Easy Elementor Addons: from n/a through <= 2.2.8.

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 Easy Elementor Addons WordPress plugin. The vulnerability allows attackers to include arbitrary local PHP files through improper control of filename parameters in include/require statements, potentially leading to remote code execution if attackers can control or upload files to be included.

MitigationUpdate Easy Elementor Addons to the latest patched version. If no patched version is available, disable the plugin immediately. As a temporary mitigation, 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. Verify Easy Elementor Addons plugin is installed
    Log in to WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'Easy Elementor Addons' in the list of active plugins.
    Affected if The plugin is installed and active in WordPress.
  2. Identify the installed plugin version
    In the WordPress admin, go to Plugins > Installed Plugins. Click on the Easy Elementor Addons plugin to view its details. The version number is displayed alongside the plugin name. Alternatively, inspect the plugin header in wp-content/plugins/easy-elementor-addons/ directory by reading the main plugin file.
    Affected if The installed version is unpatched and falls within the vulnerable version range (if known), or the version cannot be determined and the plugin is active.
  3. Check for accessible vulnerable file inclusion endpoints
    Inspect the plugin directory structure for PHP files that contain include(), require(), include_once(), or require_once() statements with unsanitized parameters. Common patterns include files in /widgets/ or /includes/ directories that accept a 'file' or 'path' parameter via GET or POST requests.
    Affected if The plugin contains PHP files that perform file inclusion using request parameters without proper validation, and these files are accessible via the web server.
  4. Test for directory traversal vulnerability
    If vulnerable endpoints are identified, send a crafted HTTP request with directory traversal sequences (e.g., ../../../../etc/passwd) in the filename parameter to test if arbitrary files can be included. Example: https://example.com/wp-content/plugins/easy-elementor-addons/includes/file.php?file=../../../../wp-config.php
    Affected if The server responds with the contents of files outside the intended directory, confirming the LFI vulnerability is exploitable.
  5. Review web server access logs for exploitation attempts
    Examine Apache/nginx access logs for requests to the Easy Elementor Addons plugin with suspicious patterns such as '../', '%2e%2e/', or attempts to include files like wp-config.php, phpinfo.php, or other sensitive local files.
    Affected if Log entries show directory traversal attempts targeting the Easy Elementor Addons plugin, indicating possible exploitation or scanning activity.

A user is affected if the Easy Elementor Addons plugin is installed and active, contains vulnerable file inclusion code, and either the version is unpatched or exploitation has been attempted.

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 Easy Elementor Addons to the latest patched version. If no patched version is available, disable the plugin immediately. As a temporary mitigation, implement web application firewall rules to block directory traversal patterns (e.g., ../) in request parameters.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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