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 (CWE-79) in the contact form. The contact form is publicly accessible without authentication, and user input is processed by nl2br() which converts newlines to <br> tags but does not escape HTML entities. The unescaped input is then inserted into a Blade email template using the {!! $msg !!} directive, allowing arbitrary HTML injection into the email body. While JavaScript execution is generally blocked by modern email clients, the injected HTML can still be rendered, enabling attackers to create phishing-like content in emails sent to administrators. This vulnerability has been fixed in commit 6c56603.
Potential Impact
The vulnerability allows attackers to inject arbitrary HTML into emails sent to administrators via the contact form. This can be leveraged to craft phishing interfaces within the email body, potentially deceiving recipients. The confidentiality of the system is at high risk due to possible phishing, but integrity impact is low and availability is unaffected. There are no known exploits in the wild as of the published date.
Mitigation Recommendations
A patch addressing this vulnerability is available in commit 6c56603 of BraveCMS-2.0. Users should upgrade to this version or later to remediate the issue. Since the vendor advisory does not specify alternative mitigations, applying the official fix is recommended. Patch status is not explicitly confirmed beyond the commit reference; users should verify the vendor repository for the official patched version.
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.
CVSS v3.1
Score 7.1high
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
BraveCMS-2.0 versions before commit 6c56603 have an XSS vulnerability (CWE-79) in the contact form. The contact form is publicly accessible without authentication, and user input is processed by nl2br() which converts newlines to <br> tags but does not escape HTML entities. The unescaped input is then inserted into a Blade email template using the {!! $msg !!} directive, allowing arbitrary HTML injection into the email body. While JavaScript execution is generally blocked by modern email clients, the injected HTML can still be rendered, enabling attackers to create phishing-like content in emails sent to administrators. This vulnerability has been fixed in commit 6c56603.
Potential Impact
The vulnerability allows attackers to inject arbitrary HTML into emails sent to administrators via the contact form. This can be leveraged to craft phishing interfaces within the email body, potentially deceiving recipients. The confidentiality of the system is at high risk due to possible phishing, but integrity impact is low and availability is unaffected. There are no known exploits in the wild as of the published date.
Mitigation Recommendations
A patch addressing this vulnerability is available in commit 6c56603 of BraveCMS-2.0. Users should upgrade to this version or later to remediate the issue. Since the vendor advisory does not specify alternative mitigations, applying the official fix is recommended. Patch status is not explicitly confirmed beyond the commit reference; users should verify the vendor repository for the official patched version.
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: 05/08/2026, 15:21:57 UTC
Last enriched: 05/16/2026, 09:42:42 UTC
Last updated: 07/31/2026, 19:22:58 UTC
Views: 74
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.