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

CVE-2025-53339

HIGH · 7.5 CVSS v3.1 Published 2025-06-27
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 devnex Devnex Addons For Elementor devnex-addons-for-elementor allows PHP Local File Inclusion.This issue affects Devnex Addons For Elementor: from n/a through <= 1.0.9.

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

Local File Inclusion (LFI) vulnerability in Devnex Addons For Elementor plugin allows attackers to include arbitrary PHP files from the server filesystem via improper control of filename parameters in include/require statements, potentially leading to remote code execution.

MitigationUpdate to the latest version of Devnex Addons For Elementor when available, or disable the plugin. If patching is delayed, implement WAF rules to block directory traversal patterns (../) in HTTP 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. Identify if Devnex Addons For Elementor is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'devnex-addons-for-elementor' or similar variant, or list all installed plugins via wp-cli: wp plugin list --status=active
    Affected if The plugin folder exists in the WordPress plugins directory and the plugin is active
  2. Determine the installed plugin version
    Read the plugin header from the main PHP file (usually wp-content/plugins/devnex-addons-for-elementor/devnex-addons-for-elementor.php) to find the 'Version' field, or query via wp-cli: wp plugin get devnex-addons-for-elementor
    Affected if The version number is lower than the patched version (compare against official WordPress repository for the latest fixed version)
  3. Locate include/require statements handling user input
    Search the plugin directory for dynamic include/require statements using grep or similar: grep -r 'include\|require' --include='*.php' wp-content/plugins/devnex-addons-for-elementor/ | grep -E '\$_GET|\$_POST|\$_REQUEST'
    Affected if PHP files in the plugin contain include/require statements directly using request parameters without sanitization
  4. Check for vulnerable file inclusion functions
    Examine the plugin source code for patterns like include($_GET['filename']) or require($_REQUEST['file']) without proper path validation or basename() checks
    Affected if The code accepts filename parameters from HTTP requests and passes them directly to include/require without validation
  5. Verify the plugin handles file paths from requests
    Review the plugin AJAX handlers or public-facing PHP files that process file path parameters, looking for functions that load templates or partials based on request input
    Affected if The plugin processes file path parameters from HTTP requests to load template files on the server

Your environment is affected if Devnex Addons For Elementor is installed and active, the installed version lacks the patch, and the plugin processes file path parameters from HTTP requests without proper validation.

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 Devnex Addons For Elementor when available, or disable the plugin. If patching is delayed, implement WAF rules to block directory traversal patterns (../) in HTTP request parameters.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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