# CVE-2022-25356: XML external entity in n/a

> Attacker can exploit XML injection in MDaemon Security Gateway to read sensitive data or execute code.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Apr 2022
- **Updated:** 5 Sep 2025
- **Also known as:** GHSA-hp7c-9qj5-xcrq

## What is CVE-2022-25356?

CVE-2022-25356 is a medium-severity vulnerability in n/a, published on 5 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Alt-N MDaemon Security Gateway through 8.5.0 allows SecurityGateway.dll?view=login XML Injection.

Weakness: CWE-91 (XML Injection)

## Which versions are affected by CVE-2022-25356?

It affects 1 product.


Products: Altn Securitygateway.

## How do I fix CVE-2022-25356?

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

## Is CVE-2022-25356 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-25356 exists.

Public exploit code:

- Alt-n/MDaemon Security Gateway <=8.5.0 - XML Injection (nuclei): http/cves/2022/CVE-2022-25356.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-25356 and fix it if it is affected.

What it is: CVE-2022-25356 is a medium-severity vulnerability in n/a, published on 5 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-25356 exists.

Affected product: n/a. 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-2022-25356/ (Markdown: https://insights.sbomify.com/CVE-2022-25356/index.md)
```

## Sources

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

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