CVE-2025-9872
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 · uneditedInsufficient filename validation in Ivanti Endpoint Manager before 2024 SU3 SR1 and 2022 SU8 SR2 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 confidenceIvanti Endpoint Manager contains insufficient filename validation that allows a remote unauthenticated attacker to execute arbitrary code. The vulnerability requires user interaction, likely meaning a victim must interact with a malicious file or link.
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< 2022= 2022= 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 Ivanti Endpoint Manager installationLocate Ivanti Endpoint Manager in the system - typically installed as 'Ivanti Endpoint Manager' or 'LANDesk Management Suite' in Windows Programs and Features, or check services for 'LDMS' or 'Ivanti Endpoint Manager' serviceAffected if The software is installed on the system
-
Determine installed versionOpen Ivanti Endpoint Manager console, navigate to Help > About, or check Windows Registry at HKEY_LOCAL_MACHINE\SOFTWARE\LANDesk\LDMain\CurrentVersion, or check the installer log files in the installation directoryAffected if The version is any release before 2022, specifically version 2022, or specifically version 2024 (compare your version against the affected ranges: < 2022, = 2022, = 2024)
-
Verify file import or upload functionalityCheck if any component allowing file import, upload, or attachment is enabled in the Ivanti Endpoint Manager console - this includes features like software distribution, patch management import, or user-provided file handlingAffected if File import or upload features are accessible to users (the filename validation flaw would apply to any such file handling module)
-
Review user access to vulnerable componentsExamine which user roles have access to file-based operations - check console permissions for standard users or restricted administrators who can import packages, patches, or configuration filesAffected if Any non-administrator or low-privilege user can access file import/upload functionality (unauthenticated attacker would need user to interact with malicious file)
-
Check for recent connection attemptsReview Ivanti Endpoint Manager server logs and IIS/Apache access logs for unusual POST requests or file upload attempts targeting the console, particularly those with abnormal filename patternsAffected if Suspicious file upload attempts or anomalous requests are found in logs
Your environment is affected if Ivanti Endpoint Manager version is less than 2022, exactly 2022, or exactly 2024 AND the system has any file import/upload functionality enabled that users can access.
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 · scoped2022
Upgrade Ivanti Endpoint Manager to version 2024 SU3 SR1 or 2022 SU8 SR2 or later. Apply the vendor patch in a staged manner starting with non-production environments.
2024 SU3 SR1 or 2022 SU8 SR2
- 1. Back up the Ivanti Endpoint Manager database and configuration before starting the update
- 2. Review the release notes for 2024 SU3 SR1 (or 2022 SU8 SR2 depending on your current version) for any specific prerequisites or migration requirements
- 3. Download the appropriate update package from the official Ivanti downloads portal (requires valid support account)
- 4. Apply the update following Ivanti's standard update procedures for Endpoint Manager
- 5. After update completion, verify the installed version shows 2024 SU3 SR1 or 2022 SU8 SR2 in the console
- 6. Test core functionality to confirm the update was successful
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing6.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 $5,312.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9872 — 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-9872 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