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

CVE-2026-7460

HIGH · 7.4 CVSS v4.0 Published 2026-05-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/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
mailcow-dockerized contains a stored cross-site scripting vulnerability in the administrator Queue Manager. The Queue Manager fetches mail queue entries from /api/v1/get/mailq/all, copies server-controlled Postfix queue fields into DataTables rows, and renders several of those fields as HTML without adequate output encoding. This issue affects mailcow-dockerized: 2026-03b.

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

mailcow-dockerized contains a stored XSS vulnerability in the administrator Queue Manager. The API endpoint /api/v1/get/mailq/all returns mail queue entries with Postfix queue fields that are rendered as HTML in DataTables rows without proper output encoding, allowing attackers to inject malicious scripts via queue field data.

MitigationImplement proper output encoding (e.g., HTML entity encoding) for all Postfix queue fields before rendering them in DataTables, or upgrade to a patched version when released.

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
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:H/VI:H/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Confirm mailcow-dockerized installation
    Identify if mailcow-dockerized is deployed in your environment. Check for docker containers running mailcow services: `docker ps --filter 'name=mailcow'`.
    Affected if mailcow-dockerized containers are running in your environment
  2. Check mailcow version
    Run `cd /opt/mailcow-dockerized && git pull && git describe --tags` or check the mailcow UI footer for version information. Compare against any known affected versions.
    Affected if installed version contains the vulnerable Queue Manager code without output encoding fixes
  3. Verify Queue Manager access
    Log in as an administrator and navigate to the Queue Manager (typically under the Mailcow UI admin section). Confirm the endpoint /api/v1/get/mailq/all is accessible.
    Affected if administrator can access the Queue Manager and retrieve mail queue data
  4. Inspect DataTables rendering for XSS vulnerability
    View the page source or network responses for the Queue Manager. Examine the JavaScript that renders Postfix queue fields (From, To, Subject, etc.) in DataTables. Check if values are inserted using innerHTML or similar methods without HTML encoding.
    Affected if queue data is rendered using methods that insert unescaped HTML (e.g., innerHTML with raw data) rather than textContent or equivalent escaping
  5. Test API response for unescaped characters
    Query the API endpoint /api/v1/get/mailq/all directly (requires admin auth). Examine the JSON response for queue entries. Then check how the frontend displays these fields in the browser.
    Affected if queue metadata fields contain raw characters that could be executed as script when rendered in the DataTables

You are affected if mailcow-dockerized is installed, the Queue Manager is accessible to administrators, and the Postfix queue fields are rendered in DataTables without HTML escaping of special characters.

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

Implement proper output encoding (e.g., HTML entity encoding) for all Postfix queue fields before rendering them in DataTables, or upgrade to a patched version when released.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7460 — 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-7460 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