dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2025-62383

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 · high confidence

SQL injection vulnerability in Ivanti Endpoint Manager prior to version 2024 SU5 allows an authenticated remote attacker to inject malicious SQL queries through unsanitized input, enabling extraction of arbitrary data from the database.

MitigationUpdate Ivanti Endpoint Manager to version 2024 SU5 or later. Additionally, review database logs for suspicious queries and audit user accounts to ensure no compromise occurred.

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 Ivanti Endpoint Manager version
    Check the installed version through the product's About dialog, help menu, or system information page within the EPM console. Alternatively, check the installer or version file if accessible.
    Affected if The version is any release of 2024 (including 2024.0, 2024.1, etc.) or any version prior to 2024, and the installed version is earlier than 2024 SU5.
  2. Confirm the specific update level
    Determine if the installation is at SU5 (Service Update 5) or later by reviewing the full version string, which typically includes the SU build number in the format '2024 SU5' or similar.
    Affected if The version displays as 2024 without SU5, or shows a build number earlier than the SU5 release.
  3. Verify remote access exposure
    Determine if the EPM web console or remote access interfaces are accessible from the network. Check firewall rules, IIS/Apache bindings, and the EPM server configuration for exposed endpoints.
    Affected if The EPM console is reachable remotely and the vulnerability is network-exploitable without requiring local console access.
  4. Review database query logs
    Examine SQL Server or the database backend logs for Ivanti Endpoint Manager. Look for unusual or malformed SQL statements, especially those containing UNION SELECT, DROP, or extraction patterns from non-standard tables.
    Affected if Suspicious SQL queries appear in logs that do not match known application behavior, particularly from user sessions that could indicate exploitation.
  5. Audit user accounts
    Review user accounts in the EPM administrative console for unauthorized accounts, privilege escalations, or accounts created around the time of potential exploitation.
    Affected if Unknown administrative accounts exist, or existing accounts show unexpected privilege changes.

The environment is affected if Ivanti Endpoint Manager is installed at any version prior to 2024 SU5 and is exposed to remote authenticated attackers who could inject SQL through unsanitized input fields.

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

Update Ivanti Endpoint Manager to version 2024 SU5 or later. Additionally, review database logs for suspicious queries and audit user accounts to ensure no compromise occurred.

Recommended fix High confidence

2024 SU5 (Service Update 5) or later

  1. 1. Identify current Ivanti Endpoint Manager version via the administration console or by checking the installation
  2. 2. Confirm the installed version is before 2024 SU5 (Service Update 5)
  3. 3. Obtain the 2024 SU5 update package from the official Ivanti download portal or through your licensed distribution channel
  4. 4. Review Ivanti's official upgrade documentation and release notes for 2024 SU5
  5. 5. Perform a full backup of the Endpoint Manager database and configuration before proceeding
  6. 6. Apply the 2024 SU5 update following Ivanti's standard upgrade procedure
  7. 7. Verify the upgrade was successful by confirming the new version in the administration console
  8. 8. Test critical functionality to ensure normal operations are restored
Caveat Review release notes for any configuration or feature changes between your current version and 2024 SU5; standard upgrade precautions apply

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

Fix this in Endpoint Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,820
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-62383 — 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-62383 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