CVE-2025-40725
BaseFortify
Publication date: 2025-09-10
Last updated on: 2025-09-11
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 |
|---|---|---|
| azon | dominator | * |
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-40725 is a reflected Cross-Site Scripting (XSS) vulnerability in Azon Dominator, a PHP script for affiliate websites. It allows an attacker to execute arbitrary JavaScript code in a victim's browser by sending a malicious URL that manipulates the “q” parameter in the /search endpoint via a GET request. This means the attacker can run scripts in the context of the victim's browser session. [1]
How can this vulnerability impact me? :
This vulnerability can be exploited to steal sensitive user data such as session cookies, which can lead to account hijacking. It can also enable attackers to perform unauthorized actions on behalf of the user, potentially compromising user accounts and data integrity. [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 with a crafted GET request that manipulates the "q" parameter to include JavaScript code and observing if the code is executed or reflected in the response. For example, you can use curl to send a request like: curl -i "http://your-target/search?q=<script>alert(1)</script>" and check if the script is reflected in the response. 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?
The immediate step to mitigate this vulnerability is to update Azon Dominator to the latest version where the issue has been fixed. Until the update can be applied, you should consider implementing input validation and output encoding on the "q" parameter in the /search endpoint to prevent execution of injected scripts. Additionally, applying web application firewall (WAF) rules to block malicious payloads targeting the "q" parameter can help reduce risk. [1]