Skip to main content
VulnerabilityPublished Updated

CVE-2026-41576: Ajax30 BraveCMS-2.0 · Cross-site Scripting

Affects Ajax30 BraveCMS-2.0Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Ajax30BraveCMS-2.0Affected
  • =< 6c5660373cf5f0ca9181603280427aca46ef11ea
Fixed in–

AI-suggested

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.

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.

References

Community reviews

Loading reviews…