Pending AnalysisCVE-2026-3425

CVE-2026-3425: LFI in RTMKit Addons for Elementor

Platform

wordpress

Component

rometheme-for-elementor

Fixed in

2.0.3

CVE-2026-3425 describes a Local File Inclusion (LFI) vulnerability affecting the RTMKit Addons for Elementor plugin for WordPress. This vulnerability allows authenticated attackers with Author-level access or higher to include and execute arbitrary PHP files on the server. The vulnerability impacts versions 0 through 2.0.2 of the plugin, and a patch is available in version 2.0.3.

WordPress

Detect this CVE in your project

Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.

Impact and Attack Scenarios

Successful exploitation of CVE-2026-3425 grants an attacker the ability to execute arbitrary PHP code on the server. This can lead to a complete compromise of the WordPress site, including data exfiltration, modification of website content, and installation of malicious software. The attacker, being authenticated with Author-level access, can leverage this vulnerability to bypass access controls and potentially escalate privileges. The blast radius extends to any sensitive data stored within the WordPress database or accessible through the web server’s file system. This vulnerability shares similarities with other LFI exploits where attackers leverage file inclusion to execute malicious code and gain control of the system.

Exploitation Context

CVE-2026-3425 was published on May 13, 2026. Severity is rated HIGH with a CVSS score of 8.8. Currently, there are no publicly known active campaigns targeting this vulnerability. The vulnerability is not listed on KEV (Known Exploited Vulnerabilities) as of this writing. Public Proof-of-Concept (POC) code is likely to emerge given the ease of exploitation inherent in LFI vulnerabilities.

Threat Intelligence

Exploit Status

Proof of ConceptUnknown
CISA KEVNO
Internet ExposureHigh
Reports1 threat report

CISA SSVC

Exploitationnone
Automatableno
Technical Impacttotal

CVSS Vector

THREAT INTELLIGENCE· CVSS 3.1CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H8.8HIGHAttack VectorNetworkHow the attacker reaches the targetAttack ComplexityLowConditions required to exploitPrivileges RequiredLowAuthentication level needed to attackUser InteractionNoneWhether a victim must take actionScopeUnchangedImpact beyond the vulnerable componentConfidentialityHighRisk of sensitive data exposureIntegrityHighRisk of unauthorized data modificationAvailabilityHighRisk of service disruptionnextguardhq.com · CVSS v3.1 Base Score
What do these metrics mean?
Attack Vector
Network — remotely exploitable over the internet. No physical or local access required. Widest attack surface.
Attack Complexity
Low — no special conditions required. Attacker can exploit reliably without depending on rare configurations or timing.
Privileges Required
Low — any valid user account is sufficient. Basic authenticated access required.
User Interaction
None — attack is automatic and silent. Victim does nothing: no click, no file open.
Scope
Unchanged — impact is limited to the vulnerable component itself.
Confidentiality
High — complete confidentiality loss. Attacker can read all data: credentials, keys, personal data.
Integrity
High — attacker can write, modify, or delete any data: databases, config files, or code.
Availability
High — complete crash or resource exhaustion. Full denial of service.

Affected Software

Componentrometheme-for-elementor
Vendorwordfence
Maximum version2.0.2
Fixed in2.0.3

Weakness Classification (CWE)

Timeline

  1. Reserved
  2. Published
  3. Modified

Mitigation and Workarounds

The primary mitigation for CVE-2026-3425 is to immediately upgrade the RTMKit Addons for Elementor plugin to version 2.0.3 or later. If upgrading is not immediately feasible due to compatibility issues or breaking changes, consider restricting file upload permissions within the WordPress environment to prevent attackers from uploading malicious PHP files that can be included. Implement a Web Application Firewall (WAF) with rules to block requests containing suspicious file paths or patterns in the 'path' parameter of the 'get_content' AJAX action. Thoroughly review and sanitize all user inputs to prevent malicious code injection.

How to fix

Update to version 2.0.3, or a newer patched version

Frequently asked questions

What is CVE-2026-3425 — LFI in RTMKit Addons for Elementor?

CVE-2026-3425 is a Local File Inclusion vulnerability in the RTMKit Addons for Elementor WordPress plugin allowing authenticated attackers to execute arbitrary PHP code. It affects versions 0–2.0.2 and has a CVSS score of 8.8, indicating high severity.

Am I affected by CVE-2026-3425 in RTMKit Addons for Elementor?

You are affected if your WordPress site uses the RTMKit Addons for Elementor plugin and is running version 0 through 2.0.2. Check your plugin version immediately to determine your risk level.

How do I fix CVE-2026-3425 in RTMKit Addons for Elementor?

Upgrade the RTMKit Addons for Elementor plugin to version 2.0.3 or later. If immediate upgrade is not possible, implement temporary mitigations like WAF rules and restricted file upload permissions.

Is CVE-2026-3425 being actively exploited?

As of the current assessment, CVE-2026-3425 is not known to be actively exploited in the wild, but the ease of exploitation suggests it could become a target.

Where can I find the official RTMKit advisory for CVE-2026-3425?

Refer to the official RTMKit Addons for Elementor plugin website or the WordPress plugin repository for the latest advisory and update information regarding CVE-2026-3425.

Is your project affected?

Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.

WordPress

Detect this CVE in your project

Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.

livefree scan

Scan your WordPress project now — no account

Upload any manifest (composer.lock, package-lock.json, WordPress plugin list…) or paste your component list. You get a vulnerability report instantly. Uploading a file is just the start: with an account you get continuous monitoring, Slack/email alerts, multi-project and white-label reports.

Manual scanSlack/email alertsContinuous monitoringWhite-label reports

Drag & drop your dependency file

composer.lock, package-lock.json, requirements.txt, Gemfile.lock, pubspec.lock, Dockerfile...