# CVE-2026-41576: Ajax30/BraveCMS-2.0: Stored HTML Injection in Contact Email via nl2br() and Unescaped Blade Template

> Attackers can inject HTML into contact emails to create phishing interfaces, requiring a patch to sanitize user input.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 May 2026
- **Updated:** 13 May 2026
- **Also known as:** GHSA-x7cg-8grr-grvx

## What is CVE-2026-41576?

CVE-2026-41576 is a high-severity cross-site scripting vulnerability in Ajax30 BraveCMS-2.0, published on 8 May 2026. An attacker can exploit it over the internet without logging in, 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, the contact form is publicly accessible (no authentication required). User-supplied message text is passed through PHP's nl2br() function, which converts newlines to <br> tags but does not escape HTML. The resulting string is then passed to a Blade email template using the unescaped {!! $msg !!} directive. The resulting content is then rendered in a Blade email template using the unescaped {!! $msg !!} directive. Because HTML is not sanitized, arbitrary markup can be injected into the email body. While modern HTML-capable email clients (Gmail or Outlook Web) typically block JavaScript execution, they still render HTML content. This allows attackers to craft convincing phishing interfaces inside the email sent to the administrator. 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-41576?


## How do I fix CVE-2026-41576?

No fix has been published for CVE-2026-41576 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-41576 being exploited?

There is no known exploitation of CVE-2026-41576 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41576 is a high-severity cross-site scripting vulnerability in Ajax30 BraveCMS-2.0, published on 8 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-41576 in the wild and no public exploit code.

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-41576/ (Markdown: https://insights.sbomify.com/CVE-2026-41576/index.md)
```

## Sources

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

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