# CVE-2022-3980: XML external entity in Sophos Mobile managed on-premises

> An XML External Entity vulnerability in Sophos Mobile allows attackers to perform server-side request forgery and potentially execute code.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Nov 2022
- **Updated:** 29 Apr 2025
- **Also known as:** GHSA-965x-72v5-49v5

## What is CVE-2022-3980?

CVE-2022-3980 is a critical vulnerability in Sophos Mobile managed on-premises, published on 16 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An XML External Entity (XEE) vulnerability allows server-side request forgery (SSRF) and potential code execution in Sophos Mobile managed on-premises between versions 5.0.0 and 9.7.4.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

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

It affects 1 product.


Products: Sophos Mobile.

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

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

## Is CVE-2022-3980 being exploited?

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

Public exploit code:

- Sophos Mobile managed on-premises - XML External Entity Injection (nuclei): http/cves/2022/CVE-2022-3980.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3980 is a critical vulnerability in Sophos Mobile managed on-premises, published on 16 Nov 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-3980 exists.

Affected product: Sophos Mobile managed on-premises. 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-3980/ (Markdown: https://insights.sbomify.com/CVE-2022-3980/index.md)
```

## Sources

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

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