CVE-2026-41524: high-severity vulnerability in Ajax30 BraveCMS-2.0
Ajax30/BraveCMS-2.0: Stored XSS in Page / Article Content
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.7epss 0.3%
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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N
Affected products
Ajax30 · BraveCMS-2.0Related CVEs — Ajax30 BraveCMS-2.0
In the same product, most dangerous first.
CVE-2026-35164HIGHBrave CMS Sffected by Unrestricted File Upload via CKEditor EndpointEPSS 0.7%CVE-2026-35047CRITICALBrave CMS has Unrestricted File Upload in BraveCMS via CKEditor EndpointEPSS 0.6%CVE-2026-35182HIGHMissing Authorization Privilege EscalationEPSS 0.3%CVE-2026-41576HIGHAjax30/BraveCMS-2.0: Stored HTML Injection in Contact Email via nl2br() and Unescaped Blade TemplateEPSS 0.3%CVE-2026-35183HIGHBrave CMS has an Insecure Direct Object Reference in Article Image DeletionEPSS 0.2%