cve.bz

CVE-2025-55147 ivanti: Cross Site Reference Forgery

8.8 highEPSS 0.6%

High (8.8) in ivanti. EPSS 0.6% estimated probability of exploitation activity in the next 30 days.

On this page
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 sensitive actions on behalf of the victim user. User interaction is required

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 51st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2025-09-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-352 Cross-Site Request Forgery (Cross Site Reference Forgery)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-55147 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-55147?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-55147?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-55147 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
ivanti:connect_securebefore 22.7
ivanti:connect_secure22.7
ivanti:connect_secure22.7:r1
ivanti:connect_secure22.7:r1.1
ivanti:connect_secure22.7:r1.2
ivanti:connect_secure22.7:r1.3
ivanti:connect_secure22.7:r1.4
ivanti:connect_secure22.7:r1.5
ivanti:connect_secure22.7:r2
ivanti:connect_secure22.7:r2.1
ivanti:connect_secure22.7:r2.2
ivanti:connect_secure22.7:r2.3
ivanti:connect_secure22.7:r2.4
ivanti:connect_secure22.7:r2.5
ivanti:connect_secure22.7:r2.6
ivanti:connect_secure22.7:r2.7
ivanti:connect_secure22.7:r2.8
ivanti:policy_securebefore 22.7
ivanti:policy_secure22.7
ivanti:policy_secure22.7:r1
ivanti:policy_secure22.7:r1.1
ivanti:policy_secure22.7:r1.2
ivanti:policy_secure22.7:r1.3
ivanti:policy_secure22.7:r1.4
ivanti:policy_secure22.7:r1.5
ivanti:zero_trust_access_gateway22.8:r2.2
ivanti:neurons_for_secure_accessbefore 22.8
ivanti:neurons_for_secure_access22.8:r1
ivanti:neurons_for_secure_access22.8:r1.1
ivanti:neurons_for_secure_access22.8:r1.2
ivanti:neurons_for_secure_access22.8:r1.3

Attack patterns (CAPEC)

  • CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
  • CAPEC-111 JSON Hijacking (aka JavaScript Hijacking) Likelihood: High · Severity: High
  • CAPEC-462 Cross-Domain Search Timing Severity: Medium
  • CAPEC-467 Cross Site Identification Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON