Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Lifecycle Timeline
2DescriptionCVE.org
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.
AnalysisAI
Local File Inclusion vulnerability in RTMKit Addons for Elementor plugin versions up to 2.0.2 allows authenticated attackers with Author-level privileges to include and execute arbitrary PHP files via the 'path' parameter in the 'get_content' AJAX action, enabling remote code execution. The vulnerability requires low-privilege WordPress account access (Author role or higher) and has a CVSS score of 8.8, indicating high impact across confidentiality, integrity, and availability. EPSS data not available, but exploitation requires specific WordPress role assignment, limiting attack surface to sites where untrusted users have Author-level access. No active exploitation confirmed by CISA KEV at time of analysis.
Technical ContextAI
This vulnerability affects the RTMKit Addons for Elementor WordPress plugin (CPE: cpe:2.3:a:rometheme:rtmkit), specifically the PluginApi.php file handling AJAX requests. The flaw is a classic CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program) where the 'get_content' AJAX action accepts user-controlled input via the 'path' parameter without proper validation or sanitization. In WordPress environments, AJAX actions are exposed endpoints that authenticated users can invoke. The vulnerable code at line 50 of PluginApi.php likely uses PHP include(), require(), or similar file inclusion functions with the unsanitized 'path' parameter, allowing attackers to traverse the filesystem and include arbitrary PHP files. When PHP files are included, their code executes in the context of the web server process, granting full application-level access. This is particularly dangerous in WordPress environments where file upload capabilities combined with LFI create a complete remote code execution chain.
RemediationAI
Update RTMKit Addons for Elementor plugin to version 2.0.3 or later, which addresses the vulnerability per the WordPress plugin repository changeset 3474369 visible at https://plugins.trac.wordpress.org/changeset/3474369/. Review the changeset to confirm the exact fix version number before deployment. If immediate patching is not feasible, implement these compensating controls with noted trade-offs: First, audit and restrict WordPress Author role assignments to only fully trusted users, understanding this may disrupt multi-author workflows and guest posting capabilities. Second, implement Web Application Firewall (WAF) rules to block requests to WordPress AJAX endpoints containing suspicious 'path' parameters with directory traversal sequences (../, absolute paths, or PHP file extensions), though this may cause false positives with legitimate plugin functionality. Third, use file integrity monitoring to detect unauthorized PHP file uploads and modifications, providing detection but not prevention. Fourth, disable PHP execution in WordPress upload directories via .htaccess or web server configuration (e.g., 'php_flag engine off' for Apache or 'location ~* ^/wp-content/uploads/.*\.php$ { deny all; }' for nginx), which prevents execution of uploaded PHP files but may break legitimate plugins requiring PHP execution in uploads. Review all existing Author-level accounts for signs of compromise. Consult the official Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/396ecd5b-d351-4289-aea4-332af5101f10?source=cve for additional guidance.
sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not
(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear
ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C
Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au
Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c
Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
NetAlertX (formerly PiAlert) versions 23.01.14 through 24.x before 24.10.12 allow unauthenticated command injection thro
The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all
Same weakness CWE-98 – PHP Remote File Inclusion
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-29937