CVE-2025-40726
BaseFortify
Publication date: 2025-06-16
Last updated on: 2025-06-16
Assigner: Spanish National Cybersecurity Institute, S.A. (INCIBE)
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
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-40726 is a reflected Cross-Site Scripting (XSS) vulnerability in the Nosto eCommerce platform, specifically in the /pages/search-results-page endpoint. It allows remote attackers to inject and execute arbitrary malicious scripts by manipulating the 'q' GET request parameter. This means that when a user visits a specially crafted URL, the injected script can run in their browser, potentially leading to unauthorized actions or data theft. [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 visit a maliciously crafted URL on the affected Nosto platform. This can lead to theft of sensitive information such as cookies or session tokens, unauthorized actions performed on your behalf, or redirection to malicious sites, 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 sending crafted HTTP requests to the /pages/search-results-page endpoint with malicious scripts injected into the 'q' GET parameter and observing if the script is reflected and executed. For example, you can use curl to test this: curl -i 'http://targetsite/pages/search-results-page?q=<script>alert(1)</script>' and check the response for the injected script. Additionally, web vulnerability scanners that test for reflected XSS can be used to detect this issue. [1]
What immediate steps should I take to mitigate this vulnerability?
Since no patch or solution has been reported at this time, immediate mitigation steps include implementing input validation and output encoding on the 'q' parameter to prevent script injection, applying web application firewall (WAF) rules to block malicious payloads targeting this endpoint, and educating users to avoid clicking on suspicious links. Monitoring and restricting access to the vulnerable endpoint may also help reduce risk until a patch is available. [1]