CVE-2025-22466
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 · uneditedReflected XSS in Ivanti Endpoint Manager before version 2024 SU1 or before version 2022 SU7 allows a remote unauthenticated attacker to obtain admin privileges. User interaction is required.
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 confidenceReflected XSS vulnerability in Ivanti Endpoint Manager allows a remote unauthenticated attacker to inject malicious scripts through user interaction, potentially hijacking admin sessions and escalating privileges to full administrative access.
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 versionCheck the installed version through the product's about page, registry key (if Windows), or by querying the server directly via the web interface or administrative consoleAffected if The installed version is 2022, 2024, or any version below 2022 (the installed version falls within < 2022, = 2022, or = 2024)
-
Verify web console accessibilityConfirm the Ivanti Endpoint Manager web console is accessible by navigating to the server URL (typically ports 80/443 or configured alternate ports)Affected if The web interface is exposed and reachable (the vulnerability requires user interaction with the web interface)
-
Check network exposureDetermine if the web console is accessible from untrusted networks by reviewing firewall rules, VPN configuration, or network ACLs restricting access to the serverAffected if The web console is accessible from the internet or untrusted networks without IP restriction
-
Review for XSS indicators in logsExamine server access logs and security event logs for unusual query parameters, patterns matching script injection attempts, or unexpected references to external URLs in request fieldsAffected if Log analysis reveals suspicious XSS payload patterns or indicators of exploitation attempts
You are affected if the installed Ivanti Endpoint Manager version is 2022, 2024, or any version below 2022 AND the web console is accessible to untrusted users or networks.
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
Upgrade Ivanti Endpoint Manager to version 2024 SU1 or later, or version 2022 SU7 or later. Alternatively, implement WAF rules to filter malicious XSS payloads and restrict admin access to trusted IP ranges until patching is feasible.
2024 SU1 (or 2022 SU7 for legacy 2022 installations)
- 1. Identify the current version of Ivanti Endpoint Manager by checking the product 'About' or system information page
- 2. If running version 2024 (any patch level), upgrade to version 2024 SU1 or later
- 3. If running version 2022 (any patch level below SU7), upgrade to version 2022 SU7 or later
- 4. If running a version prior to 2022, upgrade to either 2022 SU7 or 2024 SU1 based on compatibility requirements
- 5. After upgrade, verify the new version is reflected correctly in the product console
- 6. Test that admin functionality remains operational post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22466 — 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-22466 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