# CVE-2025-7472: Privilege escalation in Sophos Intercept X for Windows Installer

> A local user can gain system privileges if the Intercept X installer is run as SYSTEM, requiring an upgrade to mitigate.

- **Severity:** High 7.5 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Jul 2025
- **Updated:** 17 Jul 2025
- **Also known as:** GHSA-q389-vcr6-qv93

## What is CVE-2025-7472?

CVE-2025-7472 is a high-severity vulnerability in Sophos Intercept X for Windows Installer, published on 17 Jul 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A local privilege escalation vulnerability in the Intercept X for Windows installer prior version 1.22 can lead to a local user gaining system level privileges, if the installer is run as SYSTEM.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2025-7472?


## How do I fix CVE-2025-7472?

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

## Is CVE-2025-7472 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-7472 and fix it if it is affected.

What it is: CVE-2025-7472 is a high-severity vulnerability in Sophos Intercept X for Windows Installer, published on 17 Jul 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-7472 in the wild and no public exploit code.

Affected product: Sophos Intercept X for Windows Installer. 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-2025-7472/ (Markdown: https://insights.sbomify.com/CVE-2025-7472/index.md)
```

## Sources

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

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