dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-9809

HIGH · 7.6 CVSS v3.1 Published 2026-05-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A stored Cross-Site Scripting (XSS) vulnerability exists in the Projects component of Mautic 7. When displaying project tags and popovers on administrative detail views (such as campaigns, emails, or forms), user-supplied project names are rendered without proper sanitization. An authenticated user with permissions to create or edit projects can exploit this to inject malicious script payloads. When an administrative user views an entity associated with a compromised project and hovers over its tag, the injected script executes within the context of their active browser session. This could allow an attacker to perform administrative actions on behalf of the victim, alter system configurations, or exfiltrate sensitive data.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A stored XSS vulnerability in Mautic 7's Projects component allows authenticated users with project create/edit permissions to inject malicious JavaScript into project names. When administrative users view entities (campaigns, emails, forms) associated with compromised projects and hover over project tags or popovers, the injected script executes within their authenticated browser session.

MitigationApply proper output encoding/sanitization to all project name rendering in tags and popover contexts within the Projects component, or upgrade to a patched Mautic version if available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Mautic 7 is installed
    Locate the Mautic installation directory and check the version file (typically version.txt or composer.json in the root directory) or access the admin dashboard footer which often displays the version
    Affected if The installed version is Mautic 7.x (any minor version)
  2. Confirm Projects component is enabled
    Log into the Mautic admin panel and navigate to the main menu to verify the 'Projects' option is visible and accessible in the sidebar navigation
    Affected if The Projects menu item exists and is accessible to your user account
  3. Check user permissions for project management
    Go to Users > Roles or Users > Permissions in the admin panel and examine whether any role has 'Projects: Create' or 'Projects: Edit' permissions granted
    Affected if At least one active user role has project create or edit permissions enabled
  4. Inspect database for suspicious project names
    Query the project table (typically 'projects' in the Mautic database) and examine the 'name' column for any project entries containing HTML script tags, javascript: URIs, or event handler attributes like onload/onerror/onmouseover
    Affected if Any project record contains raw HTML script tags or JavaScript event handlers in the name field
  5. Review recent project creation/modification activity
    Check the Mautic audit log (Settings > Audit Log) for recent entries involving the projects table, looking for test or suspicious-sounding project names that may indicate vulnerability testing
    Affected if Recent audit log entries show project names with unusual characters or patterns that could be XSS payloads

You are affected if you are running Mautic 7.x with the Projects component enabled and users exist who have project create/edit permissions, as the XSS can be triggered when administrative users view project tags.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply proper output encoding/sanitization to all project name rendering in tags and popover contexts within the Projects component, or upgrade to a patched Mautic version if available.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9809 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9809 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data