CVE-2026-16787 json
Live Composer <= 2.1.19 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'dslc_custom_field' Shortcode
published 2026-09-01 2 mo ago modified 2026-09-02 2 mo ago also EUVD-2026-68975
- cvss
- 6.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 26%
- public exploits
- 0
- none known
Summary
The Live Composer – Free WordPress Website Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'dslc_custom_field' Shortcode in all versions up to, and including, 2.1.19 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 mo ago
Exploit prediction
0.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N |
Affected products
- livecomposer Live Composer – Free WordPress Website Builder
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/91febd9e-0b46-4f67-9ba0-97c01bf1c699?source=cve
- plugins.trac.wordpress.org /browser/live-composer-page-builder/tags/2.1.18/includes/shortcodes.php#L89
- plugins.trac.wordpress.org /browser/live-composer-page-builder/tags/2.1.18/includes/shortcodes.php#L84
- plugins.trac.wordpress.org /browser/live-composer-page-builder/tags/2.1.18/includes/shortcodes.php#L88
- plugins.trac.wordpress.org /changeset?reponame=&old=3662813%40live-composer-page-builder&new=3662813%40live-composer-page-builder
Sources
- CVE List CVE-2026-16787
- NVD CVE-2026-16787
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.