CVE-2026-41524 Ajax30/BraveCMS-2.0: Stored XSS in Page / Article Content
Stored XSS in Brave CMS allows editor-role users to inject scripts that execute in visitors' browsers, potentially leading to session hijacking or malicious actions.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2026-41524?
CVE-2026-41524 is a high-severity cross-site scripting vulnerability in Ajax30 BraveCMS-2.0, published on 8 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official 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.
Weakness: CWE-79
Which versions are affected by CVE-2026-41524?
How do I fix CVE-2026-41524?
No fix has been published for CVE-2026-41524 yet. Limit exposure of the affected software until one is available.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2026-41524 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41524 exists.
Sources
Also known as GHSA-xj46-722x-6433.