CVE-2026-3426

RTMKit Addons for Elementor <= 2.0.2 - Authenticated (Author+) Missing Authorization to Widget Configuration Modification

2026-05-12 00:00
momopon1415

Strategic Overview

Status
Patched in 2.0.3
Affected Plugin
RTMKit
Affected Version
<= 2.0.2
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-3426
View all RTMKit vulnerabilities

At a glance

CVE-2026-3426 is a medium-severity Missing Authorization vulnerability in the RTMKit WordPress plugin, affecting versions <= 2.0.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 2.0.3; sites on affected versions should update now. Disclosed May 2026, reported by momopon1415.

Vulnerability Overview

The RTMKit Addons for Elementor plugin for WordPress is vulnerable to unauthorized modification of data due to missing capability checks on the save_widget() and reset_all_widgets() functions in all versions up to, and including, 2.0.2. This makes it possible for authenticated attackers, with Author-level access and above, to modify or reset site-wide widget configurations.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-862: Missing Authorization

RTMKit <= 2.0.2 carries this weakness at save_widget(), and reaching it takes an account at Author level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For RTMKit the fix is 2.0.3: builds <= 2.0.2 are affected, anything from 2.0.3 onward is not.

Remediation

Update to version 2.0.3, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: RTMKit 2.0.3 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C