CVE-2025-8712
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 · uneditedMissing authorization in Ivanti Connect Secure before 22.7R2.9 or 22.8R2, Ivanti Policy Secure before 22.7R1.6, Ivanti ZTA Gateway before 22.8R2.3-723 and Ivanti Neurons for Secure Access before 22.8R1.4 (Fix deployed on 02-Aug-2025) allows a remote authenticated attacker with read-only admin privileges to configure restricted settings.
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 confidenceMissing authorization in Ivanti Connect Secure, Policy Secure, ZTA Gateway, and Neurons for Secure Access allows authenticated read-only admin users to configure restricted settings that should require elevated privileges. This is a privilege escalation vulnerability where the authorization check is not properly enforced on certain configuration endpoints.
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.8= 22.8< 22.7= 22.7< 22.7= 22.7= 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Ivanti product and versionAccess the admin console or check system information. For Connect Secure/Policy Secure, go to System > Status or check the welcome page. For ZTA Gateway or Neurons for Secure Access, check the system dashboard or run: 'show version' via CLI or check the About page in the web UI.Affected if The version matches any of the affected ranges: Neurons For Secure Access < 22.8 or = 22.8; Connect Secure < 22.7 or = 22.7; Policy Secure < 22.7 or = 22.7; ZTA Gateway = 22.8
-
Confirm read-only admin accounts existLog into the admin console and navigate to Users > Administrators or Administration > Administrators. Look for accounts with role 'Read Only Administrator' or equivalent read-only role.Affected if Any read-only administrator accounts are configured on the system
-
Verify read-only admins can access restricted configuration endpointsUsing a read-only admin account, attempt to access or modify settings that should require elevated privileges, such as: System > Configuration > Network Settings, or Security Settings, or Authentication/Authorization policies. Try to POST or modify configuration values through the API or web interface that should be restricted to full administrators.Affected if A read-only admin can successfully modify or save restricted configuration settings that should only be writable by administrators with elevated privileges
-
Check audit logs for unauthorized configuration changesReview System > Logs > Admin Access Logs or similar audit logs. Look for configuration change events where the user account has a read-only role.Affected if Configuration changes are logged as being performed by read-only administrator accounts
A user is affected if the installed product version falls within the affected ranges AND read-only administrator accounts can modify restricted configuration settings that should require elevated privileges.
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 patches: Ivanti Connect Secure 22.7R2.9/22.8R2, Policy Secure 22.7R1.6, ZTA Gateway 22.8R2.3-723, and Neurons for Secure Access 22.8R1.4. After patching, verify that read-only admin accounts can no longer modify restricted settings.
22.7R2.9/22.8R2 (Connect Secure), 22.7R1.6 (Policy Secure), 22.8R2.3-723 (ZTA Gateway), 22.8R1.4 (Neurons for Secure Access)
- 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 22.8R2.3-723 or later
- 5. For Neurons for Secure Access: upgrade to version 22.8R1.4 or later
- 6. After upgrade, verify the read-only admin role can no longer modify restricted settings
- 7. Review admin role permissions to ensure least-privilege access controls are properly enforced
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-8712 — 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-8712 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