CVE-2025-55143
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 text injection in Ivanti Connect Secure before 22.7R2.9 or 22.8R2, Ivanti Policy Secure before 22.7R1.6, Ivanti ZTA Gateway before 2.8R2.3-723 and Ivanti Neurons for Secure Access before 22.8R1.4 (Fix deployed on 02-Aug-2025) allows a remote unauthenticated attacker to inject arbitrary text into a crafted HTTP response. 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 text injection vulnerability in multiple Ivanti products (Connect Secure, Policy Secure, ZTA Gateway, and Neurons for Secure Access) allows unauthenticated remote attackers to inject arbitrary text into HTTP responses via unsanitized user input that gets reflected in the response. 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.
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< 22.7= 22.7< 22.7= 22.7= 22.8< 22.8= 22.8CVSS 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.
-
Identify the installed Ivanti productAccess the web administration interface or check system documentation to determine which product is deployed: Connect Secure, Policy Secure, ZTA Gateway, or Neurons for Secure AccessAffected if Any of these four Ivanti products are in use
-
Check Ivanti Connect Secure versionLog into the admin UI and navigate to System > Configuration > System Platform, or run 'dp get version' from the CLIAffected if Version is less than 22.7, equal to 22.7, or falls between 22.7 and 22.7R2.9 (not patched)
-
Check Ivanti Policy Secure versionLog into the admin UI and navigate to System > Configuration > System Platform, or run 'dp get version' from the CLIAffected if Version is less than 22.7, equal to 22.7, or falls between 22.7 and 22.7R1.6 (not patched)
-
Check Ivanti ZTA Gateway versionAccess the admin interface or check the system information page to identify the version numberAffected if Version is exactly 22.8 and has not been updated to 2.8R2.3-723 or higher
-
Check Ivanti Neurons for Secure Access versionAccess the admin interface or check the system information page to identify the version numberAffected if Version is less than 22.8, equal to 22.8, or between 22.8 and 22.8R1.4 (not patched)
-
Verify the web interface is accessible to unauthenticated usersConfirm whether the login page or other public-facing endpoints accept user input that could be reflected in the HTTP response without sanitizationAffected if The product is vulnerable to unauthenticated reflected text injection via user input on public-facing pages
Your environment is affected if you are running any of the four listed products (Connect Secure, Policy Secure, ZTA Gateway, Neurons for Secure Access) with version numbers matching the affected ranges and the web interface is accessible to unauthenticated 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 · scoped22.722.8
Apply vendor-supplied patches: upgrade Ivanti Connect Secure to 22.7R2.9/22.8R2+, Policy Secure to 22.7R1.6+, ZTA Gateway to 2.8R2.3-723+, and Neurons for Secure Access to 22.8R1.4+ (all patches deployed 02-Aug-2025).
Connect Secure: 22.7R2.9 or 22.8R2 | Policy Secure: 22.7R1.6 | ZTA Gateway: 2.8R2.3-723 | Neurons for Secure Access: 22.8R1.4
- 1. Identify the specific Ivanti product in use (Connect Secure, Policy Secure, Zero Trust Access Gateway, or Neurons for Secure Access)
- 2. Determine the current installed version from the admin console or system settings
- 3. Download the appropriate fixed version from the Ivanti customer portal or authorized download channels
- 4. Review the upgrade guide for your specific product in the Ivanti documentation
- 5. Schedule a maintenance window as upgrades may require downtime
- 6. Back up the current configuration before proceeding
- 7. Apply the upgrade following the product-specific installation instructions
- 8. After upgrade, verify the new version is installed correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-55143 — 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-55143 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