CVE-2025-10573
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 · uneditedStored XSS in Ivanti Endpoint Manager prior to version 2024 SU4 SR1 allows a remote unauthenticated attacker to execute arbitrary JavaScript in the context of an administrator session. 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 confidenceA stored cross-site scripting (XSS) vulnerability in Ivanti Endpoint Manager prior to version 2024 SU4 SR1 allows an unauthenticated remote attacker to inject malicious JavaScript that executes within an administrator's browser session when they interact with the affected interface.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Ivanti Endpoint Manager installationLocate the Ivanti Endpoint Manager installation by checking for the Core Server service or Console application, typically installed in C:\Program Files\Ivanti\Endpoint Manager or via Windows Services (service name often contains 'LANDESK' or 'Ivanti').Affected if The product is installed and running.
-
Identify installed versionAccess the administrator console, then navigate to the About or System Information page (usually Help > About Ivanti Endpoint Manager) to view the exact version number and build. Alternatively, check the registry key HKLM\SOFTWARE\LANDesk\ManagementSuite\Version or examine the Core Server installation directory for version files.Affected if Version cannot be determined or shows as 2024 (any build) or any version prior to 2024 SU4 SR1.
-
Compare against affected version rangeReview the version identified in step 2. Affected versions are: all releases prior to 2024, and version 2024 (including all SU1-SU3 service updates). The fixed version is 2024 SU4 SR1 or later.Affected if The installed version falls within the < 2024 or = 2024 range, meaning they are vulnerable.
-
Verify administrative interface accessibilityConfirm the Ivanti Endpoint Manager web console or client is accessible to users who could be targeted. The stored XSS executes when an administrator interacts with the affected interface.Affected if The administrative console is accessible and the product is in use.
If the installed Ivanti Endpoint Manager version is 2024 or any version prior to 2024 SU4 SR1, the environment is affected by this stored XSS vulnerability.
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
Upgrade Ivanti Endpoint Manager to version 2024 SU4 SR1 or later to remediate this vulnerability.
Ivanti Endpoint Manager 2024 SU4 SR1 or later
- Check current Ivanti Endpoint Manager version via the admin console or system information
- Download Ivanti Endpoint Manager 2024 SU4 SR1 or later from the official Ivanti download portal
- Review Ivanti upgrade documentation and release notes for version 2024 SU4 SR1
- Back up the current Ivanti Endpoint Manager database and configuration
- Schedule upgrade during planned maintenance window
- Run the upgrade installer following Ivanti's standard upgrade procedure
- After upgrade, verify the version shows 2024 SU4 SR1 or later in the admin console
- Log in as administrator and confirm the XSS vulnerability is remediated by checking that the specific vulnerable component now properly encodes user input
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10573 — 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-10573 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