CVE-2026-41576: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in Ajax30 BraveCMS-2.0
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.
AI Analysis
Technical Summary
BraveCMS-2.0 versions before commit 6c56603 have an XSS vulnerability in the contact form. User-supplied message text is processed with nl2br(), which converts newlines to <br> tags but does not sanitize HTML. The unsanitized message is then embedded in an email template using Blade's unescaped {!! $msg !!} directive, enabling injection of arbitrary HTML markup into emails sent to administrators. While JavaScript execution is typically blocked by modern email clients, the ability to inject HTML can facilitate phishing attacks by crafting deceptive email content. The issue is fixed in commit 6c56603.
Potential Impact
An attacker can inject arbitrary HTML markup into emails sent to administrators via the contact form, potentially enabling phishing attacks through crafted email content. The vulnerability does not allow JavaScript execution in modern email clients but still poses a risk due to HTML rendering. Confidentiality impact is high due to potential phishing, integrity impact is low, and availability is not affected.
Mitigation Recommendations
This vulnerability has been patched in BraveCMS-2.0 as of commit 6c56603. Users should update to this version or later to remediate the issue. No additional mitigation actions are indicated by the vendor advisory.
CVE-2026-41576: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in Ajax30 BraveCMS-2.0
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
BraveCMS-2.0 versions before commit 6c56603 have an XSS vulnerability in the contact form. User-supplied message text is processed with nl2br(), which converts newlines to <br> tags but does not sanitize HTML. The unsanitized message is then embedded in an email template using Blade's unescaped {!! $msg !!} directive, enabling injection of arbitrary HTML markup into emails sent to administrators. While JavaScript execution is typically blocked by modern email clients, the ability to inject HTML can facilitate phishing attacks by crafting deceptive email content. The issue is fixed in commit 6c56603.
Potential Impact
An attacker can inject arbitrary HTML markup into emails sent to administrators via the contact form, potentially enabling phishing attacks through crafted email content. The vulnerability does not allow JavaScript execution in modern email clients but still poses a risk due to HTML rendering. Confidentiality impact is high due to potential phishing, integrity impact is low, and availability is not affected.
Mitigation Recommendations
This vulnerability has been patched in BraveCMS-2.0 as of commit 6c56603. Users should update to this version or later to remediate the issue. No additional mitigation actions are indicated by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-21T14:15:21.958Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69fdff95cbff5d8610e6d6f5
Added to database: 5/8/2026, 3:21:57 PM
Last enriched: 5/8/2026, 3:37:10 PM
Last updated: 5/9/2026, 3:49:58 AM
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.