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

CVE-2026-3425

HIGH · 8.8 CVSS v3.1 Published 2026-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
The RTMKit Addons for Elementor plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 2.0.2 via the 'path' parameter of the 'get_content' AJAX action. This makes it possible for authenticated attackers, with Author-level access and above, to include and execute arbitrary PHP files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where PHP files can be uploaded and included.

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 · high confidence

The RTMKit Addons for Elementor WordPress plugin versions up to 2.0.2 contains a Local File Inclusion vulnerability in the 'get_content' AJAX action via the 'path' parameter. Authenticated attackers with Author-level access or higher can exploit this to include and execute arbitrary PHP files on the server, achieving remote code execution.

MitigationUpdate the plugin to version 2.0.3 or later which contains the patch. If an update is unavailable, disable the plugin. Implement Web Application Firewall rules to block suspicious 'get_content' AJAX requests with directory traversal patterns.

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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. Confirm RTMKit Addons plugin is installed
    Navigate to WordPress admin > Plugins and locate 'RTMKit Addons for Elementor' or inspect the plugin directory at wp-content/plugins/ for a folder matching 'rtmkit' or similar naming
    Affected if The plugin appears in the installed plugins list
  2. Check installed plugin version
    Open the main plugin file (usually plugin-name.php) or readme.txt in the plugin directory and locate the version declaration comment
    Affected if Version is 2.0.2 or lower, or no version is displayed (indicating an old unpatched release)
  3. Verify the get_content AJAX endpoint exists
    Check the plugin source code for a registered AJAX action handler for 'get_content' (look for add_action('wp_ajax_get_content') or 'wp_ajax_nopriv_get_content')
    Affected if The AJAX action handler for 'get_content' is present in the plugin code
  4. Inspect path parameter handling in get_content handler
    Locate the function handling the get_content AJAX action and examine how the 'path' parameter is processed - look for include, require, or similar file inclusion functions using this parameter
    Affected if The 'path' parameter is used directly in file inclusion functions without proper sanitization or validation
  5. Test if directory traversal is possible
    If you have access to testing, send an AJAX request to admin-ajax.php with action=get_content and a path value like ../../../wp-config.php to see if the response includes file contents
    Affected if The response reveals contents of files outside the intended directory, confirming the LFI vulnerability

You are affected if the RTMKit Addons plugin is installed at version 2.0.2 or lower AND the get_content AJAX action exists with vulnerable path parameter handling that allows directory traversal.

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 version 2.0.3 or later which contains the patch. If an update is unavailable, disable the plugin. Implement Web Application Firewall rules to block suspicious 'get_content' AJAX requests with directory traversal patterns.

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-2026-3425 — 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-2026-3425 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