CVE-2025-62389
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 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 installationLocate the Ivanti Endpoint Manager installation in your environment. Check for the core application server or console components.Affected if Ivanti Endpoint Manager is not installed - not affected. If installed, continue to version check.
-
Determine installed versionAccess the Ivanti Endpoint Manager console or use the built-in version check feature (typically via Help > About or similar). Identify the exact version number including any Service Update (SU) designation.Affected if The installed version is 2024 without SU5 applied, or any version prior to 2024 - likely affected. Versions 2024 SU5 and later are NOT affected.
-
Verify authentication configurationReview the Ivanti Endpoint Manager authentication settings. Check if user accounts with database-facing privileges are configured and accessible remotely.Affected if Remote authentication is enabled and valid user accounts exist - attacker could potentially authenticate and exploit. If only local console access is permitted with no remote authentication, exploitation is less likely but not impossible.
-
Check database connectivity configurationInspect the database connection settings within the Ivanti Endpoint Manager administration console. Confirm the database type and connection method used.Affected if Database connectivity is configured and the application connects to a SQL database - potential target for SQL injection. The vulnerability allows reading sensitive data from this database.
You are affected if Ivanti Endpoint Manager version 2024 (without SU5) or any prior version is installed and remote authentication is enabled, as this allows 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 Ivanti Endpoint Manager 2024 SU5 or later to patch the SQL injection vulnerability. Verify all database-facing input is properly parameterized after upgrade.
Ivanti Endpoint Manager 2024 SU5 (Service Update 5) or later
- Verify current Ivanti Endpoint Manager version by navigating to Admin > System > Server Information in the console
- Download Ivanti Endpoint Manager 2024 SU5 (or later) from the Ivanti portal or official distribution channels
- Review Ivanti upgrade documentation and release notes for 2024 SU5
- Create a full backup of the database and configuration before proceeding
- Schedule a maintenance window as upgrades may require downtime
- Run the upgrade installer on the primary server following Ivanti's documented upgrade procedure
- Verify the upgrade completed successfully by checking the version in the console
- Test critical functionality to ensure the upgrade did not introduce issues
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.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 $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62389 — 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-62389 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