CVE-2026-35009
Reflected XSS in Open ISES Tickets
Publication date: 2026-05-20
Last updated on: 2026-05-20
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openises | tickets | to 3.44.2 (exc) |
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-2026-35009 is a reflected cross-site scripting (XSS) vulnerability found in Open ISES Tickets versions before 3.44.2, specifically in the add_note.php file.
The vulnerability occurs because the ticket_id parameter in the URL is not properly sanitized before being inserted into a hidden input field's VALUE attribute. This allows an authenticated attacker to inject arbitrary JavaScript code.
When a victim visits a maliciously crafted URL containing the injected JavaScript payload in the ticket_id parameter, the script executes in their browser.
How can this vulnerability impact me? :
This vulnerability can allow attackers to execute arbitrary JavaScript code in the context of the victim's browser session.
- Steal sensitive information such as session cookies or authentication tokens.
- Perform actions on behalf of the victim within the application.
- Potentially redirect users to malicious sites or display fraudulent content.
Overall, it can lead to compromised user accounts and unauthorized access to sensitive data.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by identifying URLs that include the ticket_id parameter in the add_note.php page of Open ISES Tickets before version 3.44.2. Specifically, look for URLs where the ticket_id parameter contains suspicious or unexpected JavaScript code.
One way to detect exploitation attempts on your network is to monitor HTTP requests for patterns where the ticket_id parameter includes JavaScript payloads.
- Use web server logs or network monitoring tools to search for requests matching: add_note.php?ticket_id=<script>
- Example command using grep on web server logs: grep -i 'add_note.php?ticket_id=' /var/log/apache2/access.log | grep -E '<script|%3Cscript'
- Use a web vulnerability scanner to test the add_note.php endpoint by injecting JavaScript payloads into the ticket_id parameter and observing if the payload is reflected.
What immediate steps should I take to mitigate this vulnerability?
The immediate step to mitigate this vulnerability is to upgrade Open ISES Tickets to version 3.44.2 or later, where the reflected cross-site scripting issue in add_note.php has been patched.
Until the upgrade can be applied, consider restricting access to the affected add_note.php page to trusted users only and monitor for suspicious activity involving the ticket_id parameter.
Additionally, implement web application firewall (WAF) rules to detect and block requests containing suspicious JavaScript code in the ticket_id parameter.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability described is a reflected cross-site scripting (XSS) issue that allows authenticated attackers to inject arbitrary JavaScript code via an unsanitized ticket_id parameter. Such vulnerabilities can potentially lead to unauthorized access to user data or session hijacking, which may impact the confidentiality and integrity of personal or sensitive information.
While the provided information does not explicitly mention compliance with standards like GDPR or HIPAA, XSS vulnerabilities generally pose risks to data protection and privacy requirements mandated by these regulations. Exploitation of this vulnerability could lead to unauthorized disclosure or manipulation of personal data, thereby potentially violating compliance obligations.
The patch released in version 3.44.2 addresses this and other vulnerabilities, improving overall security posture and helping to mitigate risks that could affect regulatory compliance.