CVE-2025-40638
Reflected XSS in Eventobot /search-results Enables Data Theft
Publication date: 2026-03-09
Last updated on: 2026-03-10
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 |
|---|---|---|
| sbitsoft | eventobot | * |
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?
[{'type': 'paragraph', 'content': 'CVE-2025-40638 is a reflected Cross-Site Scripting (XSS) vulnerability found in Eventobot, an event management and ticket sales platform.'}, {'type': 'paragraph', 'content': "This vulnerability occurs through the 'name' parameter in the '/search-results' endpoint, where an attacker can send a malicious URL that executes arbitrary JavaScript code in the victim's browser."}, {'type': 'paragraph', 'content': 'The attacker can exploit this flaw to steal sensitive user data such as session cookies or perform actions on behalf of the user.'}] [1]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to execute malicious JavaScript code in your browser when you click on a specially crafted URL.
As a result, attackers can steal sensitive information like session cookies, which may lead to account hijacking.
Additionally, attackers can perform unauthorized actions on your behalf within the Eventobot platform.
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?
I don't know
What immediate steps should I take to mitigate this vulnerability?
The vulnerability has been addressed and fixed by the Eventobot development team in the latest software version.
To mitigate this vulnerability, you should update Eventobot to the latest version where the issue is resolved.