CVE-2025-55888
BaseFortify
Publication date: 2025-09-22
Last updated on: 2025-10-14
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ard | gec_en_ligne | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include sanitizing and encoding the accountName field in the Ajax response to prevent script injection. Additionally, monitoring and filtering Ajax responses for malicious scripts and applying security patches or updates from the vendor when available are recommended. Using Content Security Policy (CSP) headers to restrict script execution can also help reduce risk. [1]
Can you explain this vulnerability to me?
CVE-2025-55888 is a Cross-Site Scripting (XSS) vulnerability in the Ajax transaction manager endpoint of ARD. The vulnerability occurs because the accountName field in the Ajax response is not properly sanitized or encoded before being rendered in users' browsers. An attacker can intercept the Ajax response and inject malicious JavaScript code into this field, which then executes in the context of the user's browser. [1]
How can this vulnerability impact me? :
This vulnerability can lead to session hijacking, cookie theft, and other malicious actions by allowing attackers to execute arbitrary JavaScript in users' browsers. This can compromise user accounts and sensitive information. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by intercepting and inspecting Ajax responses from the transaction manager endpoint, specifically looking at the accountName field for unsanitized or suspicious JavaScript code. Using tools like a web proxy (e.g., Burp Suite or OWASP ZAP) to capture and analyze Ajax responses can help identify injected scripts. There are no specific commands provided in the resources, but using interception proxies to monitor HTTP responses is recommended. [1]