CVE-2025-56762
BaseFortify
Publication date: 2025-09-19
Last updated on: 2025-10-03
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| paracrawl | keops | 2 |
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
Can you explain this vulnerability to me?
The vulnerability in Paracrawl KeOPs v2 is a Cross Site Scripting (XSS) issue in the error.php script. It occurs because the application does not properly sanitize the 'code' parameter, allowing attackers to inject malicious JavaScript code. This injected script can then execute in the user's browser, potentially leading to unauthorized actions such as data theft or manipulation of the web page content. [1]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to execute arbitrary scripts in your browser when you visit a manipulated URL. This can lead to theft of sensitive data, hijacking of user accounts, and unauthorized changes to the content displayed on the website, potentially compromising your security and privacy. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the error.php script for improper sanitization of the 'code' parameter. A common method is to inject a script payload into the URL parameter and observe if it executes. For example, accessing the URL /error.php?code=\"><script>alert(document.domain)</script> can reveal if the XSS vulnerability exists. Network or web application scanners that test for reflected XSS by injecting scripts into URL parameters can also be used. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include sanitizing and validating the 'code' parameter in error.php to prevent injection of malicious scripts. Implement proper output encoding to ensure that any user-supplied input is safely handled before rendering in the browser. Additionally, applying web application firewall (WAF) rules to block suspicious script injections and updating the application to a patched version (if available) are recommended. [1]