CVE-2025-55147
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 · uneditedCSRF 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 execute sensitive actions on behalf of the victim user. 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 confidenceCross-Site Request Forgery (CSRF) vulnerability in multiple Ivanti products (Connect Secure, Policy Secure, ZTA Gateway, and Neurons for Secure Access) allows a remote unauthenticated attacker to trick authenticated users into unknowingly executing sensitive actions via malicious requests. The attacker exploits the lack of proper CSRF token validation on state-changing operations, using the victim's valid session cookies to perform actions like configuration changes or administrative tasks.
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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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 the Ivanti productAccess the administration interface or check system documentation to determine which product is deployed: Connect Secure, Policy Secure, Zero Trust Access Gateway, or Neurons for Secure Access.Affected if Any of the four affected products is installed.
-
Determine installed versionLog into the admin console or check the system version file. For Connect Secure/Policy Secure: typically found in System > Maintenance > Software/System Management. For ZTA Gateway/Neurons: check the web UI dashboard or /etc/version file.Affected if A version number is returned.
-
Compare version to affected rangesMatch your installed version against: Connect Secure < 22.7 or = 22.7; Policy Secure < 22.7 or = 22.7; ZTA Gateway = 22.8; Neurons for Secure Access < 22.8 or = 22.8.Affected if Your version falls within any of these ranges.
-
Verify authenticated session handlingExamine the HTTP response headers for Set-Cookie directives on sensitive endpoints (admin actions, configuration changes). Check if SameSite attribute is set on session cookies.Affected if Cookies lack SameSite=Strict or SameSite=Lax attributes, indicating weaker protection against CSRF.
-
Confirm state-changing operations lack CSRF tokensSubmit a legitimate state-changing request (such as saving a configuration) and inspect the HTTP request/response. Look for a_csrf_token or similar anti-CSRF parameter in the request body or headers.Affected if No anti-CSRF token is required or validated for administrative actions.
If your installed version matches any of the affected ranges and session cookies or CSRF tokens are not properly enforced, your environment is vulnerable to CVE-2025-55147.
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-provided patches (22.7R2.9 or 22.8R2 for Connect Secure; 22.7R1.6 for Policy Secure; 2.8R2.3-723 for ZTA Gateway; 22.8R1.4 for Neurons) released on 02-Aug-2025. Additionally, implement SameSite cookie attributes and anti-CSRF tokens on all sensitive endpoints as defense-in-depth.
Product-specific: Connect Secure to 22.7R2.9/22.8R2+; Policy Secure to 22.7R1.6+; ZTA Gateway to 2.8R2.3-723+; Neurons for Secure Access to 22.8R1.4+
- 1. Identify the exact Ivanti product and version currently deployed (Connect Secure, Policy Secure, ZTA Gateway, or Neurons for Secure Access)
- 2. For Connect Secure: upgrade to version 22.7R2.9 or 22.8R2 or later
- 3. For Policy Secure: upgrade to version 22.7R1.6 or later
- 4. For Zero Trust Access Gateway: upgrade to version 2.8R2.3-723 or later
- 5. For Neurons for Secure Access: upgrade to version 22.8R1.4 or later
- 6. After upgrade, verify the new version is running and test that CSRF protections are functioning
- 7. Review any post-upgrade configuration requirements in Ivanti release notes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-55147 — 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-55147 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