dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2025-62386

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-13
Fix available
A fix is available. Upgrade to 2024 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
SQL 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 confidence

SQL injection vulnerability in Ivanti Endpoint Manager prior to version 2024 SU5 allows an authenticated remote attacker to execute arbitrary SQL queries, enabling unauthorized data exfiltration from the database.

MitigationApply Ivanti Endpoint Manager 2024 SU5 or later patch. Restrict network access to the management interface to trusted personnel only until the patch is applied.

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
Endpoint ManagerApplication
Affected:< 2024= 2024

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Ivanti Endpoint Manager version
    Access the product console or check the installation via the About section in the management interface, or run: launchpad.exe /version (or equivalent version command for the installation). Compare the displayed version to the 2024 SU5 release.
    Affected if The installed version is 2024 (any sub-version like SU1-SU4) or any version prior to 2024.
  2. Verify the management console is network-accessible
    Determine if the Ivanti Endpoint Manager web console (typically ports 80/443 or configured HTTP/HTTPS ports) is exposed to network access beyond trusted internal networks. Check firewall rules and network segmentation configurations.
    Affected if The management interface is reachable from untrusted networks or the internet.
  3. Confirm authentication is enabled for the console
    Verify that the built-in or integrated authentication mechanism is active for the Endpoint Manager console. Ensure that anonymous or default credentials are not in use.
    Affected if Authentication is disabled or weak/default credentials are in place, allowing unauthorized access.
  4. Check for recent unauthorized database access indicators
    Review database logs, especially SQL query logs, for unexpected or unauthorized SQL commands executed against the backend database. Look for unusual SELECT, INSERT, UPDATE, or DELETE statements outside normal operational patterns.
    Affected if Suspicious or unauthorized SQL queries appear in the database or application logs.

You are affected if your Ivanti Endpoint Manager version is 2024 (any build) or earlier, and the management console is accessible with valid authentication credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2024 or later
Fixed in 2024
Interim mitigation

Apply Ivanti Endpoint Manager 2024 SU5 or later patch. Restrict network access to the management interface to trusted personnel only until the patch is applied.

Recommended fix High confidence

Endpoint Manager 2024 SU5 (Service Update 5)

  1. 1. Back up the current Ivanti Endpoint Manager database and configuration according to Ivanti documentation.
  2. 2. Download Ivanti Endpoint Manager version 2024 SU5 (Service Update 5) from the Ivanti download portal or support site.
  3. 3. Review the Ivanti Endpoint Manager 2024 SU5 release notes for any pre-installation requirements or known issues.
  4. 4. Apply the update following the standard Ivanti upgrade procedure for your deployment type (standalone or distributed).
  5. 5. Verify the upgrade completed successfully by checking the console version and confirming core functionality works.
  6. 6. Validate that the SQL injection vulnerability is remediated by confirming the fix is applied.
Caveat Review release notes for any configuration or feature changes between your current version and 2024 SU5

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Endpoint Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-62386 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-62386 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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