Skip to main content
VulnerabilityPublished

CVE-2026-9281: Master Addons For Elementor (WordPress plugin) · Cross-site Scripting

Affects Master Addons For Elementor (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.4 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
6.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
litonice13Master Addons For Elementor – Widgets, Extensions, Theme Builder, Popup Builder & Template KitsAffected
  • <=3.1.0
Fixed in–

AI-suggested

Users should monitor the vendor's advisory for updates. Until a fix is available, restrict author-level access to trusted users only and consider disabling or limiting use of the Custom JS Extension feature. Applying strict input validation and output escaping at the application level may help mitigate risk.

Description

The Master Addons For Elementor plugin for WordPress contains a stored cross-site scripting (XSS) vulnerability in the 'jtlma_custom_js' Page Setting. This affects all versions up to and including 3.1.0. Authenticated users with author-level access or higher can inject arbitrary JavaScript code via a crafted POST request, bypassing UI restrictions. The vulnerability arises from insufficient input sanitization and output escaping, and improper enforcement of capability checks during the save process. This can lead to script execution in the context of users visiting the affected pages.

References

Community reviews

Loading reviews…