CVE-2025-9713
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 · uneditedPath traversal in Ivanti Endpoint Manager before version 2024 SU4 allows a remote unauthenticated attacker to achieve remote code execution. User interaction is required.
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 path traversal vulnerability in Ivanti Endpoint Manager versions prior to 2024 SU4 allows an unauthenticated remote attacker to achieve arbitrary code execution on the target system. The vulnerability requires user interaction, likely involving a victim accessing a malicious resource that triggers the path traversal to write or execute arbitrary code.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2024= 2024CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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.
-
Identify installed EPM versionLog into the Ivanti Endpoint Manager console and navigate to the About or System Information section, or check the Windows Programs and Features list for the installed versionAffected if The version displayed is earlier than 2024 SU4 (any version < 2024 or version 2024 without SU4)
-
Check EPM server build numberIn the EPM console, go to Administration > System Overview or check the version information in the software itself to confirm the full version string including the service update numberAffected if The build or service update number is below SU4 (for example, SU1, SU2, SU3, or no SU indicated)
-
Verify patch statusReview any patch management or update history within the EPM environment to confirm whether the 2024 SU4 update has been appliedAffected if No record exists of the 2024 SU4 patch being installed, or the last applied update predates it
If the installed Ivanti Endpoint Manager version is 2024 without SU4, or any version prior to 2024, the environment is vulnerable to this path traversal flaw.
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 · scoped2024
Upgrade Ivanti Endpoint Manager to version 2024 SU4 or later. As a secondary control, implement network segmentation and restrict access to the EPM server to minimize the attack surface while the patch is being applied.
2024 SU4 (Endpoint Manager 2024 Service Update 4)
- Obtain Ivanti Endpoint Manager 2024 SU4 from the official Ivanti portal or support channels
- Review the 2024 SU4 release notes and upgrade documentation for any specific requirements
- Perform a complete backup of the current Endpoint Manager database and configuration
- Test the upgrade in a non-production environment first
- Apply the 2024 SU4 upgrade to the production Endpoint Manager instance following Ivanti's documented upgrade procedures
- Verify the upgrade completed successfully and all services are running
- Confirm the version is now 2024 SU4
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,520.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9713 — 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-9713 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