CVE-2025-7433
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA local privilege escalation vulnerability in Sophos Intercept X for Windows with Central Device Encryption 2025.1 and older allows arbitrary code execution.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA local privilege escalation vulnerability in Sophos Intercept X for Windows with Central Device Encryption versions 2025.1 and older allows authenticated local attackers to execute arbitrary code with elevated privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Sophos Intercept X with Central Device Encryption is installedOpen Windows Settings > Apps & features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | DisplayName' in PowerShell to list installed software. Look for 'Sophos Intercept X for Windows with Central Device Encryption' in the results.Affected if The product is not found in the installed programs list, then this CVE does not apply.
-
Retrieve the installed version numberRun 'Get-ItemProperty "C:\Program Files\Sophos\Intercept X\sophos.exe" -ErrorAction SilentlyContinue | Select-Object VersionInfo' or right-click sophos.exe in that directory and view Properties > Details to find the File Version.Affected if Unable to locate the executable or version information indicates the product may not be fully installed.
-
Compare installed version against affected rangeCompare the retrieved version number to 2025.1. Versions 2025.1 and any version released prior (such as 2024.x, 2023.x, etc.) are within the affected range.Affected if The installed version is 2025.1 or older, indicating the environment is vulnerable to this privilege escalation flaw.
A defender is affected if Sophos Intercept X for Windows with Central Device Encryption is installed with version 2025.1 or any earlier version.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate Sophos Intercept X for Windows with Central Device Encryption to a version newer than 2025.1 when patches become available.
Upgrade to Sophos Intercept X for Windows with Central Device Encryption version 2025.2 or later
- Verify current Sophos Intercept X for Windows version by opening the Sophos Central agent or checking Add/Remove Programs
- Navigate to Sophos Central admin console and check for available updates
- Update to the latest available version of Sophos Intercept X with Central Device Encryption (version newer than 2025.1)
- Alternatively, enable automatic updates in Sophos Central to receive the patched version automatically
- After update, verify the new version is installed and the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7433 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-7433 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data