dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2025-22465

MEDIUM · 6.1 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 2022 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Reflected XSS in Ivanti Endpoint Manager before version 2024 SU1 or before version 2022 SU7 allows a remote unauthenticated attacker to execute arbitrary javascript in a victim's browser. Unlikely 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 confidence

Reflected XSS in Ivanti Endpoint Manager before version 2024 SU1 or 2022 SU7 allows a remote unauthenticated attacker to inject malicious JavaScript through HTTP requests that gets reflected in the application's response, enabling session hijacking, credential theft, or arbitrary actions in the victim's browser context.

MitigationApply the vendor security update (2024 SU1 or 2022 SU7) to implement proper input validation and output encoding for user-supplied parameters.

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:< 2022= 2022= 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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Confirm Ivanti Endpoint Manager is installed
    Identify the product name in your environment - look for 'Ivanti Endpoint Manager' or 'LanDesk' (previous branding) in installed programs, services, or the web application header
    Affected if The product is not Ivanti Endpoint Manager, this CVE does not apply
  2. Check the installed version
    Access the Endpoint Manager console or admin interface and navigate to the About or Version information page to determine the exact version number
    Affected if Version is 2022 (any build) or 2024 (any build), or versions below 2022 - these are in the affected range
  3. Verify if running a patched version
    Compare your version against the fixed releases: 2024 Service Update 1 (SU1) or 2022 Service Update 7 (SU7)
    Affected if Running a version below 2024 SU1 or below 2022 SU7 - meaning versions 2022 or 2024 without the specific SU patch are vulnerable
  4. Confirm web interface is accessible
    Test HTTP/HTTPS access to the Endpoint Manager web portal - this vulnerability is exploited via HTTP requests
    Affected if The web interface is exposed and reachable via HTTP/HTTPS - the attacker needs this access to send malicious requests with injected JavaScript

You are affected if you run Ivanti Endpoint Manager versions 2022 or 2024 without the SU1 or SU7 patches respectively, and your web interface is accessible to unauthenticated users.

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 2022 or later
Fixed in 2022
Interim mitigation

Apply the vendor security update (2024 SU1 or 2022 SU7) to implement proper input validation and output encoding for user-supplied parameters.

Recommended fix Moderate confidence

2024 SU1 or 2022 SU7 (depending on your current major version branch)

  1. 1. Back up your Ivanti Endpoint Manager database and configuration
  2. 2. Download the appropriate updated version from the Ivanti portal: 2024 SU1 or 2022 SU7
  3. 3. Review the upgrade documentation and release notes for any prerequisites
  4. 4. Schedule a maintenance window for the upgrade
  5. 5. Apply the upgrade following standard Ivanti upgrade procedures
  6. 6. Verify the upgrade was successful by logging into the console
  7. 7. Confirm the XSS vulnerability is patched by checking the version number in the console
Caveat Review release notes for version-specific changes; upgrade paths may have specific prerequisites or migration requirements

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

Fix this in Endpoint Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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