CVE-2025-62385
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 through unsanitized input in the application's database interactions.
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.
-
Confirm Ivanti Endpoint Manager installationLocate the Ivanti Endpoint Manager service or installation directory on the server (typically in C:\Program Files\Ivanti or the installation path configured during setup)Affected if The application is not present on the system
-
Identify installed versionAccess the Ivanti Endpoint Manager console and navigate to the About section, or check version information in the registry or installation directoryAffected if The version cannot be determined or shows 2024 without SU5 applied
-
Compare version to affected rangeCheck the exact build or Service Update (SU) version number and compare against 2024 SU5Affected if Version is 2024 (any build prior to SU5) or any version prior to 2024
-
Verify web interface accessibilityConfirm the Ivanti Endpoint Manager web console is accessible (default ports 80/443 or configured custom ports)Affected if The web interface is exposed to network access since this is a remote authenticated attack vector
-
Review authentication exposureCheck whether the application allows remote authentication, as the SQL injection requires an authenticated attackerAffected if Remote authentication to the endpoint manager console is enabled
You are affected if Ivanti Endpoint Manager is installed with version 2024 or earlier without SU5 applied and remote authentication is available.
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 this SQL injection vulnerability.
2024 SU5 (or later)
- 1. Identify the current installed version of Ivanti Endpoint Manager via the admin console or system information
- 2. Obtain Ivanti Endpoint Manager version 2024 SU5 from the official Ivanti support portal (forums.ivanti.com)
- 3. Review Ivanti's upgrade documentation and take a full backup of the database and configuration
- 4. Apply the upgrade to version 2024 SU5 following Ivanti's standard upgrade procedure
- 5. Verify the upgrade was successful by confirming the version shows 2024 SU5 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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 $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62385 — 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-62385 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