{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-41576 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-41576 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-41576 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-41576 in the wild and no public exploit code.\n\nAffected product: Ajax30 BraveCMS-2.0. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-41576/ (Markdown: https://insights.sbomify.com/CVE-2026-41576/index.md)","id":"CVE-2026-41576","markdown":"https://insights.sbomify.com/CVE-2026-41576/index.md","name":"CVE-2026-41576","record":{"aliases":["GHSA-x7cg-8grr-grvx"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Brave CMS","requires_auth":"none","summary":"Attackers can inject HTML into contact emails to create phishing interfaces, requiring a patch to sanitize user input.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"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 \u003cbr\u003e 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Ajax30/BraveCMS-2.0: Stored HTML Injection in Contact Email via nl2br() and Unescaped Blade Template","id":"CVE-2026-41576","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"authentik: SAML source does not validate Conditions, timing, or audience on assertions","id":"CVE-2026-41577"},"packages":[],"prev":{"headline":"th30d4y/IP: DOM-Based Cross-Site Scripting (XSS) Vulnerability","id":"CVE-2026-41575"},"products":["BraveCMS-2.0"],"published":"2026-05-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-13","vendors":["Ajax30"]},"summary":"Attackers can inject HTML into contact emails to create phishing interfaces, requiring a patch to sanitize user input.","url":"https://insights.sbomify.com/CVE-2026-41576/"}