CVE
postfixadmin stored XSS in email alias view
Affects PostfixAdmin 3.3 before 3.3.17 and 4.0 before 4.0.7, with a cross-site scripting issue when viewing aliases. Fixed in 3.3.17 and 4.0.7.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.0.7, 3.3.17
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Running PostfixAdmin 4.0 before 4.0.7 Running PostfixAdmin 3.3 before 3.3.17
Summary
Postfixadmin has a stored cross-site scripting flaw when viewing email aliases. A remote attacker with a low-privilege login, such as an admin account able to inject aliases, can use it to run script in a viewer's browser, with no user action needed.
Original description
A stored cross site scripting attack when viewing email aliases in postfixadmin 4.0 before 4.0.7, and postfixadmin 3.3 before 3.3.17 could be caused by signed in admins able to inject aliases.
Who should check
Teams running PostfixAdmin 4.0 before 4.0.7 or 3.3 before 3.3.17 to manage email aliases.
“patch XSS issues in 3.3.x: incorrect use of smarty escape:quotes”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.1/10CVSS 8.1, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Running PostfixAdmin 4.0 before 4.0.7 Running PostfixAdmin 3.3 before 3.3.17Upgrade to a fixed version: 4.0.7, 3.3.17.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-127178 (postfixadmin XSS issue when viewing aliases), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-127178 (entry last updated 2026-11-18):
Affected:
- postfixadmin postfixadmin: from 4.0.0, fixed in 4.0.7; from 3.3.0, fixed in 3.3.17
Fixed versions: 4.0.7, 3.3.17.
Conditions (all must be true for the bug to be hit):
- Running PostfixAdmin 4.0 before 4.0.7 (source: https://github.com/postfixadmin/postfixadmin/releases/tag/v4.0.7)
- Running PostfixAdmin 3.3 before 3.3.17 (source: https://github.com/postfixadmin/postfixadmin/releases/tag/postfixadmin-3.3.17)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-127178 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-127178 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/postfixadmin/postfixadmin/releases/tag/v4.0.7
- https://github.com/postfixadmin/postfixadmin/releases/tag/postfixadmin-3.3.17
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-127178
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-127178"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- postfixadmin
From 4.0.0 · fixed in 4.0.7; From 3.3.0 · fixed in 3.3.17
Evidence 4
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-127178 |
| Record | NVD · CVE-2026-127178 |
| Other links 2 | |
| Repository | GitHub · postfixadmin/postfixadmin · Release v4.0.7 |
| Repository | GitHub · postfixadmin/postfixadmin · Release postfixadmin-3.3.17 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-127178
Is CVE-2026-127178 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The bug is a cross-site scripting (XSS) issue on the alias view pages. Injected script can run in the browser of a user who views the affected aliases.Source: github.com, github.com
Which versions are affected by CVE-2026-127178?
postfixadmin: from 4.0.0 before 4.0.7; from 3.3.0 before 3.3.17.Source: cve.now feed data
Am I affected, and how do I check?
PostfixAdmin 4.0 before 4.0.7 and 3.3 before 3.3.17 are the affected ranges. To check, compare the installed PostfixAdmin version with these ranges.Source: github.com, github.com
How do I fix CVE-2026-127178?
Upgrade to 4.0.7 if on the 4.0 line, or to 3.3.17 if on the 3.3 line. The sources do not name separate patch IDs for this fix.Source: github.com, github.com