CVE-2025-13661
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 prior to version 2024 SU4 SR1 allows a remote authenticated attacker to write arbitrary files outside of the intended directory. 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 · high confidencePath traversal vulnerability in Ivanti Endpoint Manager prior to version 2024 SU4 SR1 allows an authenticated remote attacker to write arbitrary files outside the intended directory through manipulated file paths. User interaction is required, likely meaning the attacker needs the victim to trigger a file write operation (e.g., via a crafted file upload or download).
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
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Confirm Ivanti Endpoint Manager is installedLocate Ivanti Endpoint Manager installation by checking for the service or application binary. Common paths include C:\Program Files\Ivanti\EndpointManager or C:\Program Files (x86)\Ivanti\EndpointManager on Windows. On Linux/Unix, check /opt/ivanti or /usr/local/ivanti.Affected if Ivanti Endpoint Manager software is found on the system
-
Identify installed version numberOpen Ivanti Endpoint Manager admin console and navigate to Help > About, or check the installation directory for a version file. Alternatively, query the Windows registry key HKLM\SOFTWARE\Ivanti\EndpointManager\InstallPath or check the version info of the core executable.Affected if Unable to determine version or version is 2024 or lower (< 2024 SU4 SR1)
-
Compare version to affected rangeCompare your installed version against the affected range: versions < 2024 and version = 2024 are vulnerable. The fixed version is 2024 SU4 SR1 or later. Note that version 2024 without any service update is affected.Affected if Version is 2024 (any build) or any version prior to 2024, meaning it is prior to 2024 SU4 SR1
-
Verify file upload/download feature accessibilityCheck if the file upload, download, or package distribution feature is enabled and accessible to authenticated users. Review user role permissions in the admin console under Users > Roles or Security > Access Control.Affected if Authenticated users have access to file upload/download functionality, which is required for the attack to be exploited
-
Audit logs for suspicious file write operationsReview Ivanti Endpoint Manager logs for entries involving manipulated file paths (e.g., paths containing ../ sequences, writes to system directories outside the intended upload folder). Check logs in the installation directory under \Logs or via the console's Log Viewer.Affected if Logs show file write operations to directories outside the intended upload folder, or abnormal file path patterns with ../ sequences
User is affected if Ivanti Endpoint Manager version is 2024 or any version prior to 2024 SU4 SR1 and authenticated users can access file upload/download features.
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 SR1 or later. As an interim measure, limit user privileges, restrict network access to the management interface, and monitor for suspicious file write activities.
2024 SU4 SR1
- 1. Identify the current version of Ivanti Endpoint Manager by accessing the admin console or checking the application system information.
- 2. Navigate to the Ivanti Endpoint Manager downloads or support portal at forums.ivanti.com.
- 3. Download the upgrade package for version 2024 SU4 SR1 (Service Update 4, Service Release 1).
- 4. Review the upgrade documentation and release notes for any prerequisites or pre-upgrade requirements.
- 5. Create a full backup of the current Ivanti Endpoint Manager installation and database.
- 6. Execute the upgrade installer following the documented upgrade procedure.
- 7. Verify the upgrade was successful by checking the version number in the admin console.
- 8. Validate that the path traversal functionality has been restricted by confirming file write operations are limited to intended directories.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13661 — 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-13661 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