CVE-2025-11623
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 allows an authenticated remote attacker to execute arbitrary SQL queries, enabling unauthorized read access to the database. The vulnerability exists in versions prior to 2024 SU5 and stems from insufficient input validation in database queries.
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 the installed Ivanti Endpoint Manager versionLocate the product version through the admin console, system information, or version lookup tool provided by IvantiAffected if The installed version is 2024 or any version prior to 2024 SU5 (Service Update 5)
-
Confirm the patch level for 2024 installationsIf running version 2024, check whether Service Update 5 has been applied by reviewing the patch level or build number in the systemAffected if The version shows 2024 without SU5 applied
-
Check for exposure of the management interfaceVerify which network interfaces the Ivanti Endpoint Manager web console or API is bound to, focusing on external or untrusted network accessibilityAffected if The administrative interface is reachable from network segments that do not require strong authentication controls
-
Review database query logsExamine database transaction logs or audit trails for unusual or unauthorized SQL query patterns that may indicate exploitation attemptsAffected if Unexpected SQL commands appear in logs, especially from authenticated sessions with limited privileges
You are affected if your Ivanti Endpoint Manager version is 2024 or any version prior to 2024 SU5, as the SQL injection flaw exists in those releases due to insufficient input validation in database 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 the vendor-supplied patch (Ivanti Endpoint Manager 2024 SU5 or later) and verify that all database interactions properly use parameterized queries to prevent SQL injection.
2024 SU5 (Endpoint Manager 2024 Service Update 5)
- 1. Back up the Ivanti Endpoint Manager database and configuration
- 2. Review Ivanti Endpoint Manager 2024 SU5 release notes for any prerequisites
- 3. Download Ivanti Endpoint Manager 2024 SU5 from the Ivanti portal or authorized distribution channel
- 4. Execute the upgrade installer following Ivanti's standard upgrade procedures
- 5. Verify the upgrade completed successfully by checking the console version
- 6. Validate that core Endpoint Manager functions are operational post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing6.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 $4,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11623 — 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-11623 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