CVE-2025-13649
Stored XSS in ZeusWeb 6.1.31 Password Recovery Email Parameter
Publication date: 2026-02-11
Last updated on: 2026-03-17
Assigner: ffb98d57-deaa-4918-a669-5225ccc13e39
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| microcom360 | zeusweb | 6.1.31 |
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-13649 is a medium-severity reflected Cross-Site Scripting (XSS) vulnerability affecting ZeusWeb version 6.1.31, a web application provided by Microcom. An attacker with access to the ZeusWeb web application can inject arbitrary JavaScript code by inserting an XSS payload into the 'Email' parameter within the 'Recover password' section at the specified URL. This vulnerability allows malicious scripts to be executed in the context of the victim's browser.
How can this vulnerability impact me? :
This vulnerability can allow an attacker to execute arbitrary JavaScript code in the context of the ZeusWeb web application users. This can lead to unauthorized actions such as stealing session tokens, redirecting users to malicious sites, or performing actions on behalf of the user without their consent. Since the vulnerability is in the 'Recover password' section, it could potentially be exploited to compromise user accounts or disrupt the password recovery process.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': "The vulnerability CVE-2025-13649 is a reflected Cross-Site Scripting (XSS) issue in the ZeusWeb application version 6.1.31, specifically exploitable via the 'Email' parameter in the 'Recover password' section at the URL https://zeus.microcom.es:4040/index.html?zeus6=true."}, {'type': 'paragraph', 'content': "To detect this vulnerability on your system, you can attempt to inject a harmless JavaScript payload into the 'Email' parameter of the password recovery URL and observe if the script is executed or reflected in the response."}, {'type': 'paragraph', 'content': 'Example command using curl to test for reflected XSS:'}, {'type': 'list_item', 'content': 'curl -G --data-urlencode "Email=<script>alert(\'XSS\')</script>" "https://zeus.microcom.es:4040/index.html?zeus6=true" -v'}, {'type': 'paragraph', 'content': 'If the response contains the injected script without proper encoding or sanitization, the vulnerability is present.'}, {'type': 'paragraph', 'content': "Additionally, monitoring web application logs for unusual or suspicious input in the 'Email' parameter or using automated web vulnerability scanners that test for reflected XSS can help detect this issue."}] [4]
What immediate steps should I take to mitigate this vulnerability?
[{'type': 'paragraph', 'content': 'The vulnerability has been addressed by Microcom in ZeusWeb version 6.2.5.'}, {'type': 'paragraph', 'content': 'Since ZeusWeb is a cloud-based service managed by Microcom, end users do not need to perform any updates or patching themselves.'}, {'type': 'paragraph', 'content': 'Immediate mitigation steps include:'}, {'type': 'list_item', 'content': 'Avoid using the vulnerable version 6.1.31 if possible by confirming with Microcom that your service is running the updated version.'}, {'type': 'list_item', 'content': 'Restrict access to the web application to trusted users only, as the vulnerability requires access to the web app.'}, {'type': 'list_item', 'content': "Monitor and filter input parameters, especially the 'Email' parameter in the password recovery section, to detect and block malicious payloads."}, {'type': 'list_item', 'content': 'Report any suspicious activity or potential exploitation attempts to Microcom support.'}] [2, 4]