# CVE-2026-119531: Live Composer < 2.1.24 - Contributor+ Stored XSS via Module Area Shortcode

> Contributor-level users can store scripts via a Live Composer shortcode that run for anyone viewing the post, including administrators.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 11 Nov 2026
- **Updated:** 11 Nov 2026
- **Also known as:** GHSA-8gwf-q9gc-gx6r

## What is CVE-2026-119531?

CVE-2026-119531 is a medium-severity cross-site scripting vulnerability in Unknown Live Composer, published on 11 Nov 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The Live Composer  WordPress plugin before 2.1.24 does not escape several attributes of one of its page-builder shortcodes before outputting them inside HTML tag attributes, allowing users with the Contributor role and above to store a payload that executes in the browser of anyone who views the post, including an administrator reviewing the pending submission.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-119531?

An affected version is exposed as installed. No special setting or call is needed.


## How do I fix CVE-2026-119531?

No fix has been published for CVE-2026-119531 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119531 being exploited?

There is no known exploitation of CVE-2026-119531 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119531 and fix it if it is affected.

What it is: CVE-2026-119531 is a medium-severity cross-site scripting vulnerability in Unknown Live Composer, published on 11 Nov 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-119531 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: Unknown Live Composer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119531/ (Markdown: https://insights.sbomify.com/CVE-2026-119531/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119531
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119531
- OSV: https://osv.dev/vulnerability/CVE-2026-119531

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119531/
Summaries are generated and may contain mistakes; the official description above is the record.