CVE-2025-62387
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 · uneditedSQL injection in Ivanti Endpoint Manager before version 2024 SU5 allows a remote authenticated attacker to read arbitrary data from the database.
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 confidenceSQL injection vulnerability in Ivanti Endpoint Manager prior to version 2024 SU5 allows an authenticated remote attacker to execute arbitrary SQL queries and read sensitive data from the database.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 installationCheck for the Ivanti Endpoint Manager service or application on the system. Look for the 'Ivanti Endpoint Manager' service in Windows Services or check Program Files for the installation directory.Affected if Ivanti Endpoint Manager is not installed on the system
-
Determine the installed versionOpen the Ivanti Endpoint Manager admin console and navigate to Help > About, or check the registry key HKLM\SOFTWARE\LANDesk\LDMain\Version, or locate the coreconfig.ini file in the installation directory.Affected if The version displayed is 2024 or any version prior to 2024 SU5
-
Verify the exact patch levelIn the admin console, check the build number or SU (Service Update) version. The fixed version is 2024 SU5 or later. Compare your build against the 2024 SU5 release.Affected if The version shows 2024 without SU5, or shows a build number lower than the SU5 release build
-
Confirm remote access is enabledCheck if the Ivanti Endpoint Manager web console or remote access features are exposed. Verify in the core settings whether remote connections are allowed.Affected if Remote authentication is enabled and the version is in the affected range
The environment is affected if Ivanti Endpoint Manager is installed with a version prior to 2024 SU5 and remote authentication is accessible.
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 SU5 or later to remediate the SQL injection vulnerability. Apply least-privilege principles to database accounts and restrict administrative access in the interim.
2024 SU5 or later
- Backup your Ivanti Endpoint Manager database and configuration before proceeding
- Download Ivanti Endpoint Manager version 2024 SU5 or later from the official Ivanti download portal
- Apply the upgrade following Ivanti's standard upgrade documentation for Endpoint Manager
- Verify the upgrade was successful by checking the version number in the console
- Confirm the SQL injection vulnerability is resolved by testing the affected functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62387 — 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-62387 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