| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Ivanti Connect Secure, Policy Secure, ZTA Gateway and Neurons for Secure Access. Impacted is an unknown function. Performing a manipulation results in cross-site request forgery. This vulnerability is cataloged as CVE-2025-55147. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in Ivanti Connect Secure, Policy Secure, ZTA Gateway and Neurons for Secure Access (the affected version is unknown). This affects an unknown code. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. CWE is classifying the issue as CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. This is going to have an impact on integrity. The summary by CVE is:
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
The advisory is shared at forums.ivanti.com. This vulnerability is uniquely identified as CVE-2025-55147 since 08/07/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
The vulnerability scanner Nessus provides a plugin with the ID 264601 (Ivanti Connect Secure < 22.7R2.9 / 22.8R2 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the databases at Tenable (264601) and EUVD (EUVD-2025-27287). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.4
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.8
CNA Vector (ivanti): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 264601
Nessus Name: Ivanti Connect Secure < 22.7R2.9 / 22.8R2 Multiple Vulnerabilities
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Timeline
08/07/2025 CVE reserved09/09/2025 Advisory disclosed
09/09/2025 VulDB entry created
09/12/2025 VulDB entry last update
Sources
Advisory: forums.ivanti.comStatus: Confirmed
CVE: CVE-2025-55147 (🔒)
GCVE (CVE): GCVE-0-2025-55147
GCVE (VulDB): GCVE-100-323229
EUVD: 🔒
Entry
Created: 09/09/2025 18:02Updated: 09/12/2025 20:06
Changes: 09/09/2025 18:02 (61), 09/10/2025 08:41 (1), 09/12/2025 20:06 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.