# 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.

- **Severity:** High 8.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N`)
- **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 available:** No
- **Published:** 8 May 2026
- **Updated:** 8 May 2026
- **Also known as:** GHSA-xj46-722x-6433

## 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 (Improper Neutralization of Input During Web Page Generation)

## 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.

## Is CVE-2026-41524 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41524 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41524 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41524 exists.

Affected product: Ajax30 BraveCMS-2.0. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41524/ (Markdown: https://insights.sbomify.com/CVE-2026-41524/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41524
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41524
- OSV: https://osv.dev/vulnerability/CVE-2026-41524

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41524/
Summaries are generated and may contain mistakes; the official description above is the record.