CVE-2025-22461
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 SU1 or before version 2022 SU7 allows a remote authenticated attacker with admin privileges to achieve code execution.
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 SU1 or 2022 SU7 allows a remote authenticated attacker with admin privileges to execute arbitrary code through specially crafted SQL queries, likely via database features that enable OS command execution.
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< 2022= 2022= 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 versionAccess the Ivanti Endpoint Manager console and navigate to the About or System Information section to view the installed version number. Alternatively, check the installation directory or registry for version metadata.Affected if The installed version is 2022 (any sub-version) or 2024 (any sub-version), or any version before 2022.
-
Confirm version against patched releasesCompare the identified version against the fixed releases: 2024 SU1 (Service Update 1) or later, and 2022 SU7 (Service Update 7) or later.Affected if The version is earlier than 2022 SU7 or 2024 SU1, meaning it falls within < 2022, = 2022, or = 2024.
-
Verify admin account accessReview user accounts and privilege levels within Ivanti Endpoint Manager to determine if any accounts possess administrator-level permissions.Affected if Any authenticated admin-level accounts exist in the system, as the vulnerability requires admin privileges to exploit.
-
Inspect database logging for suspicious SQL activityEnable and review database audit logs or SQL query logs within Ivanti Endpoint Manager for unexpected or malicious SQL commands, especially those involving system commands or database features that enable OS execution.Affected if Unusual SQL queries appear in logs, particularly those attempting to invoke database command execution features.
You are affected if your Ivanti Endpoint Manager version is 2022 (any build), 2024 (any build), or any version released before 2022, and any admin-level accounts exist that could be compromised to exploit this SQL injection flaw.
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 · scoped2022
Apply the vendor-supplied patches (2024 SU1 or 2022 SU7 and later). Since admin-level access is required, limit admin账户 access, enforce least privilege, and monitor for suspicious SQL activity.
2024 SU1 or later, or 2022 SU7 or later
- Upgrade Ivanti Endpoint Manager to version 2024 SU1 or later
- Alternatively, upgrade to version 2022 SU7 or later if staying on the 2022 branch
- Verify the upgrade was successful and the version matches the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22461 — 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-22461 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