CVE-2025-40642
BaseFortify
Publication date: 2025-09-08
Last updated on: 2025-09-08
Assigner: Spanish National Cybersecurity Institute, S.A. (INCIBE)
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| webwork | webwork | * |
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?
CVE-2025-40642 is a reflected Cross-Site Scripting (XSS) vulnerability in WebWork, a PHP-based search engine script. It allows remote attackers to execute arbitrary code by injecting malicious input through the 'q' and 'engine' request parameters in the /search endpoint. This means that when a user interacts with the vulnerable search feature, an attacker can manipulate the input to run harmful scripts in the user's browser. [1]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to execute arbitrary code in the context of your browser when you use the vulnerable WebWork search feature. This can lead to theft of sensitive information, session hijacking, or other malicious actions performed on behalf of the user. However, the attack requires user interaction and has a medium severity with a CVSS score of 5.1. [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 /search endpoint of the WebWork application for reflected XSS by injecting payloads into the 'q' and 'engine' request parameters and observing if the input is improperly reflected and executed. For example, you can use curl commands to send requests with XSS payloads and check the response for script execution. Example command: curl -G 'http://target/search' --data-urlencode "q=<script>alert(1)</script>" --data-urlencode "engine=test" [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying the official patch or update provided by the WebWork manufacturer that fixes this vulnerability. Additionally, implementing input validation and output encoding on the 'q' and 'engine' parameters to prevent script injection can help mitigate the risk. Employing web application firewalls (WAF) to detect and block malicious payloads targeting these parameters is also recommended. [1]