Quick answers
- Is CVE-2026-119531 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119531 being exploited in the wild.
- How severe is CVE-2026-119531?
- Informational severity, published 11 November 2026.
- Which products and versions are affected?
- Wordpress Live Composer before 2.1.24.
- Is there a fix for CVE-2026-119531?
- Yes: fixed in 2.1.24. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-119531 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-119531?
- Check whether you run Wordpress Live Composer at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.1.24
Technical details
The vulnerability is a stored cross-site scripting (XSS) flaw in a page-builder shortcode where several attributes are not escaped before being output inside HTML tag attributes. An attacker with Contributor role or above can craft a post containing a malicious shortcode payload that persists in the database and executes in the browsers of anyone viewing the post, including administrators. This requires authentication but allows privilege escalation and account takeover vectors.
Affected products
- WordPress Live Composer before 2.1.24
Timeline
- 2026-11-09: disclosed
- 2026-11-09: patched: Fixed in version 2.1.24