dbcve.org
Connect SecureApplication · Ivanti

CVE-2025-8711

MEDIUM · 5.4 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 22.7 / 22.8 or later.
See remediation →
61/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
CSRF 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 limited 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 · high confidence

Cross-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 execute limited actions on behalf of an authenticated victim user by tricking them into clicking a malicious link or visiting a crafted webpage.

MitigationApply vendor-supplied patches: upgrade Ivanti Connect Secure to 22.7R2.9/22.8R2 or later, Policy Secure to 22.7R1.6 or later, ZTA Gateway to 2.8R2.3-723 or later, and Neurons for Secure Access to 22.8R1.4 or later.

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
Connect SecureApplication
Affected:< 22.7= 22.7
Policy SecureApplication
Affected:< 22.7= 22.7
Zero Trust Access GatewayApplication
Affected:= 22.8
Neurons For Secure AccessApplication
Affected:< 22.8= 22.8

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
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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. Identify the Ivanti product in use
    Determine which Ivanti product is deployed: Connect Secure, Policy Secure, Zero Trust Access Gateway, or Neurons for Secure Access. Check your product documentation or admin interface to confirm the product name.
    Affected if Any of these four Ivanti products are deployed in the environment
  2. Locate the installed version number
    Access the admin web console or system CLI for your Ivanti product and locate the version/build information. This is typically found in the system information, about, or status pages of the admin interface.
    Affected if Version information cannot be retrieved or shows a version within the affected ranges
  3. Compare your version to affected ranges
    Match your installed version against these ranges: Connect Secure and Policy Secure if < 22.7 or = 22.7; Zero Trust Access Gateway if = 22.8; Neurons for Secure Access if < 22.8 or = 22.8
    Affected if Your installed version falls within any of these vulnerable ranges

You are affected if you run any of the four products and your installed version exactly matches one of the listed vulnerable versions or falls below the safe threshold.

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 22.7 / 22.8 or later
Fixed in 22.722.8
Interim mitigation

Apply vendor-supplied patches: upgrade Ivanti Connect Secure to 22.7R2.9/22.8R2 or later, Policy Secure to 22.7R1.6 or later, ZTA Gateway to 2.8R2.3-723 or later, and Neurons for Secure Access to 22.8R1.4 or later.

Recommended fix High confidence

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. 1. Identify the exact product model and current firmware version from the Ivanti admin console or device status page
  2. 2. For Ivanti Connect Secure: Upgrade to version 22.7R2.9 or 22.8R2 (whichever is applicable to your release train)
  3. 3. For Ivanti Policy Secure: Upgrade to version 22.7R1.6
  4. 4. For Ivanti ZTA Gateway: Upgrade to version 2.8R2.3-723
  5. 5. For Ivanti Neurons for Secure Access: Upgrade to version 22.8R1.4
  6. 6. Download the firmware from the official Ivanti download portal (requires valid support contract)
  7. 7. Before upgrade, backup the current device configuration from the admin console
  8. 8. Schedule a maintenance window as upgrades may cause brief service interruption
Caveat Standard upgrade risks apply - ensure configuration backup before proceeding; test in non-production first if possible

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

Fix this in Connect Secure Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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