Skip to main content
VulnerabilityPublished

CVE-2026-84902: King Addons for Elementor (WordPress plugin) · Cross-Site Scripting (XSS)

Affects King Addons for Elementor (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.8 Medium : upgrade to 51.1.81 when convenient.

Data as of 2 Nov 2026, 10:58 UTC

CVSS 3.1 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 51.1.81
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Sep 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 2 Nov 2026.

What to do

Upgrade King Addons for Elementor (WordPress plugin) to 51.1.81.

Affected software

ProductAffectedFixed in
King Addons for ElementorAffected
  • <51.1.81
Fixed in
  • 51.1.81

AI-suggested

Upgrade King Addons for Elementor to version 51.1.81 or later, where the vulnerability is fixed. Versions prior to 51.1.81 are affected. No other mitigation or temporary fix is indicated. Applying the official update fully addresses the issue.

Description

The King Addons for Elementor WordPress plugin before 51.1.81 does not perform an object-level authorization check when importing template content into a page, allowing users with contributor-level access and above to overwrite the Elementor content of arbitrary posts and pages, including those owned by administrators, and to inject JavaScript through a widget setting that is output without escaping, resulting in Stored Cross-Site Scripting that executes in the session of any user who views the affected page.

References

Community reviews

Loading reviews…