CVE-2026-4914
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 N-ITSM before version 2025.4 allows a remote authenticated attacker to obtain limited information from other user sessions. 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 · moderate confidenceStored XSS vulnerability in Ivanti N-ITSM prior to version 2025.4 allows an authenticated remote attacker to inject malicious scripts into stored content. When other users view this content, the injected script executes, enabling the attacker to obtain limited information from other user sessions. User interaction is required for exploitation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 N-ITSM is installedLocate Ivanti N-ITSM in your application inventory or check system services for N-ITSM componentsAffected if Ivanti N-ITSM is present in the environment
-
Determine installed version of Ivanti N-ITSMAccess the product's about page, check installation directory for version files, or query the application via its admin interface for version informationAffected if Installed version is lower than 2025.4 (for example, 2025.3, 2025.2, earlier releases)
-
Verify authentication mechanisms are enabledCheck if user authentication is configured and active for the N-ITSM applicationAffected if Authentication is enabled and user accounts exist in the system
-
Identify accessible stored content featuresReview which modules allow users to create or upload stored content (such as tickets, notes, attachments, or custom fields) that other users can viewAffected if Features exist where users can input and store content that is displayed to other users
-
Audit recent user-submitted content for suspicious scriptsExamine stored content entries for unexpected script tags, JavaScript event handlers, or encoded payloads that may indicate exploitation attemptsAffected if Malicious script payloads are found in stored content fields visible to other users
You are affected if Ivanti N-ITSM is installed with a version lower than 2025.4 and the application allows authenticated users to create content that is stored and viewable by other users.
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 · scopedUpgrade Ivanti N-ITSM to version 2025.4 or later to receive the vendor patch that addresses this stored XSS vulnerability.
Ivanti N-ITSM version 2025.4
- Identify current Ivanti N-ITSM version by accessing the Administration or System Information page in the product UI
- Review release notes for version 2025.4 on hub.ivanti.com to understand changes and confirm the XSS fix is included
- Plan the upgrade during a maintenance window following your organization's change management process
- Back up the Ivanti N-ITSM database and configuration before upgrading
- In a non-production environment, perform a test upgrade to verify compatibility with your custom configurations
- Execute the upgrade to version 2025.4 following the official upgrade documentation
- After upgrade, verify the application loads correctly and test that the stored XSS vulnerability is remediated
- Monitor system logs for any errors post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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 $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4914 — 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-2026-4914 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