CVE-2025-62390
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 versions before 2024 SU5 allows an authenticated remote attacker to execute arbitrary SQL queries, enabling exfiltration of 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 versionCheck the product version through the administration console (Help > About) or by inspecting the installation directory for version files, or use the built-in reporting to confirm the exact build numberAffected if Version displayed is 2024 (any build before SU5) or any version lower than 2024
-
Confirm the specific SU (Service Update) buildLocate the exact build number in the system information or release notes; SU5 corresponds to a specific build threshold that must be metAffected if Build number is below the SU5 threshold for 2024, or the version string does not indicate SU5 or later
-
Verify authentication is enabledConfirm that user authentication is active for the Endpoint Manager web console or remote access interfacesAffected if Authentication is enabled and valid user accounts exist in the system (prerequisite for exploiting this authenticated SQL injection)
A system is affected if the installed Ivanti Endpoint Manager version is 2024 (pre-SU5) or any version below 2024, and user authentication is enabled for the application.
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.
2024 SU5 (Service Update 5)
- Obtain Ivanti Endpoint Manager version 2024 SU5 from the official Ivanti download portal or your licensed distribution channel
- Review the official release notes for 2024 SU5 to understand new features, deprecated functionality, and any known migration requirements
- Create a complete backup of the current Ivanti Endpoint Manager database and configuration
- Test the upgrade in a non-production environment that mirrors your production setup
- Schedule a maintenance window with appropriate stakeholders
- Execute the upgrade to version 2024 SU5 following Ivanti's documented upgrade procedures
- Verify the upgrade was successful by checking the console version and testing core functionality
- Validate that the SQL injection vulnerability is resolved by reviewing system logs for any anomalous database queries
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62390 — 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-62390 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