Analyse en attenteCVE-2026-3425

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

Plateforme

wordpress

Composant

rometheme-for-elementor

Corrigé dans

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

Détecte cette CVE dans ton projet

Téléverse ton fichier de dépendances et découvre instantanément si cette CVE et d'autres te touchent.

Impact et Scénarios d'Attaquetraduction en cours…

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.

Contexte d'Exploitationtraduction en cours…

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.

Renseignement sur les Menaces

Statut de l'Exploit

Preuve de ConceptInconnu
CISA KEVNO
Exposition InternetÉlevée
Rapports1 rapport de menace

CISA SSVC

Exploitationnone
Automatisableno
Impact Techniquetotal

Vecteur CVSS

RENSEIGNEMENT SUR LES MENACES· CVSS 3.1CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H8.8HIGHAttack VectorNetworkComment l'attaquant atteint la cibleAttack ComplexityLowConditions requises pour exploiterPrivileges RequiredLowNiveau d'authentification requisUser InteractionNoneSi une action de la victime est requiseScopeUnchangedImpact au-delà du composant affectéConfidentialityHighRisque d'exposition de données sensiblesIntegrityHighRisque de modification non autorisée de donnéesAvailabilityHighRisque d'interruption de servicenextguardhq.com · Score de base CVSS v3.1
Que signifient ces métriques?
Attack Vector
Réseau — exploitable à distance via internet. Aucun accès physique ou local requis.
Attack Complexity
Faible — aucune condition spéciale requise. Exploitable de manière fiable.
Privileges Required
Faible — tout compte utilisateur valide est suffisant.
User Interaction
Aucune — attaque automatique et silencieuse. La victime ne fait rien.
Scope
Inchangé — impact limité au composant vulnérable.
Confidentiality
Élevé — perte totale de confidentialité. L'attaquant peut lire toutes les données.
Integrity
Élevé — l'attaquant peut écrire, modifier ou supprimer toutes les données.
Availability
Élevé — panne complète ou épuisement des ressources. Déni de service total.

Logiciel Affecté

Composantrometheme-for-elementor
Fournisseurwordfence
Version maximale2.0.2
Corrigé dans2.0.3

Classification de Faiblesse (CWE)

Chronologie

  1. Réservé
  2. Publiée
  3. Modifiée

Mitigation et Contournementstraduction en cours…

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.

Comment corriger

Mettre à jour vers la version 2.0.3, ou une version corrigée plus récente

Questions fréquentestraduction en cours…

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.

Ton projet est-il affecté ?

Téléverse ton fichier de dépendances et découvre instantanément si cette CVE et d'autres te touchent.

WordPress

Détecte cette CVE dans ton projet

Téléverse ton fichier de dépendances et découvre instantanément si cette CVE et d'autres te touchent.

en directfree scan

Scannez votre projet WordPress maintenant — sans compte

scanZone.subtitle

Scan manuelSlack/email alertsContinuous monitoringWhite-label reports

Glissez-déposez votre fichier de dépendances

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