CVE-2025-62391
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 · high confidenceSQL injection vulnerability in Ivanti Endpoint Manager prior to version 2024 SU5 enables an authenticated remote attacker to execute arbitrary SQL queries, potentially exposing sensitive data stored in the connected 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.
-
Determine Ivanti Endpoint Manager versionLocate the installed version of Ivanti Endpoint Manager via the administration console, about page, or product registry. Common locations include the console header/about section, installation directory metadata, or version information in the product UI.Affected if The installed version is 2024 (any build) or any version prior to 2024, meaning it predates the 2024 SU5 patch.
-
Verify remote authentication is enabledCheck whether remote or external authentication methods (such as LDAP, RADIUS, or other network-based login mechanisms) are configured and active in the Ivanti Endpoint Manager security or authentication settings.Affected if Remote authentication is enabled, as the vulnerability requires an authenticated attacker to inject malicious SQL queries.
-
Confirm database connectivity and accountsInspect the database connection configuration in Ivanti Endpoint Manager to identify the database type, connection strings, and associated service accounts used by the application.Affected if The application connects to a database containing sensitive data, as the SQL injection could allow unauthorized data access or exposure.
-
Review SQL query loggingEnable or review SQL query logs, audit trails, or database monitoring if available, to identify any unexpected or unauthorized SQL execution patterns.Affected if Unusual or unauthorized SQL queries appear in logs, indicating potential exploitation of the SQL injection flaw.
A user is affected if their Ivanti Endpoint Manager version is 2024 or any prior version, and remote authentication is enabled, allowing an authenticated attacker to inject arbitrary SQL queries.
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
Apply vendor patch by upgrading Ivanti Endpoint Manager to version 2024 SU5 or later, following standard change management procedures.
2024 SU5 (Service Update 5)
- Back up the current Ivanti Endpoint Manager installation and database
- Review the official Ivanti upgrade documentation for Endpoint Manager 2024 SU5
- Download the 2024 SU5 update package from the Ivanti customer portal (forums.ivanti.com)
- Apply the update following Ivanti's documented upgrade procedure for Endpoint Manager
- Verify the upgrade was successful by checking the version number
- Confirm the SQL injection vulnerability is patched
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62391 — 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-62391 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