# CVE-2026-119761: Axigen Mail Server before 10.6.39 and 10.7.1 Stored XSS via Sender Display Name


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 6 Nov 2026
- **Also known as:** GHSA-rg92-ccrh-wg37

## What is CVE-2026-119761?

CVE-2026-119761 is a medium-severity vulnerability in Axigen Mail Server, published on 30 Oct 2026. 

### Official description

Axigen Mail Server WebMail before 10.6.39 and 10.7.1 contains a stored cross-site scripting vulnerability that allows unauthenticated remote attackers to inject script via unescaped sender display names in the conversation view. Attackers can send an email with HTML and script in the From display name that executes when the recipient opens the folder, enabling mailbox content theft or redirection.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-119761?


## How do I fix CVE-2026-119761?

No fix has been published for CVE-2026-119761 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119761 being exploited?

There is no known exploitation of CVE-2026-119761 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119761 and fix it if it is affected.

What it is: CVE-2026-119761 is a medium-severity vulnerability in Axigen Mail Server, published on 30 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119761 in the wild and no public exploit code.

Affected product: Axigen Mail Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119761/ (Markdown: https://insights.sbomify.com/CVE-2026-119761/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119761
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119761
- OSV: https://osv.dev/vulnerability/CVE-2026-119761

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119761/
Summaries are generated and may contain mistakes; the official description above is the record.