Quick answers
- Is CVE-2026-119073 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119073 being exploited in the wild.
- How severe is CVE-2026-119073?
- Informational severity, published 7 November 2026.
- Which products and versions are affected?
- Live Composer before 2.1.23.
- Is there a fix for CVE-2026-119073?
- Yes: fixed in 2.1.23. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-119073 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-119073?
- Check whether you run 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.23
Technical details
The vulnerability is a Stored XSS (CWE-79) in the post-listing module shortcodes due to insufficient output escaping of a pagination parameter before it is rendered in an HTML attribute. Users with Contributor role and above can inject malicious JavaScript through the shortcode pagination setting, which persists in the database and executes in the browsers of other users who view the affected page.
Affected products
- Live Composer Live Composer before 2.1.23
Timeline
- 2026-11-05: disclosed
- 2026-11-07: patched: Fix released in version 2.1.23