CVE-2026-48213
Reflected XSS in Open ISES Tickets add.php
Publication date: 2026-05-21
Last updated on: 2026-05-21
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-48213 is a reflected cross-site scripting (XSS) vulnerability found in Open ISES Tickets versions before 3.44.2, specifically in the add.php file.
This vulnerability allows authenticated attackers to inject arbitrary JavaScript code by exploiting the unsanitized ticket_id POST parameter, which is directly inserted into an HTML form input value attribute without proper neutralization.
When a victim views the crafted response, the injected JavaScript payload executes in their browser, potentially leading to malicious actions.
How can this vulnerability impact me? :
This vulnerability can impact users by allowing attackers to execute arbitrary JavaScript in the context of the victim's browser session.
Such execution can lead to theft of sensitive information, session hijacking, or performing actions on behalf of the victim without their consent.
Since the vulnerability requires authentication, attackers with valid credentials can exploit it to target other authenticated users.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for HTTP POST requests to the add.php endpoint containing the ticket_id parameter with suspicious or malicious JavaScript payloads. Since the vulnerability involves reflected cross-site scripting via the ticket_id POST parameter, inspecting web traffic for unusual or encoded script tags in this parameter can help identify exploitation attempts.
A practical approach is to use web proxy tools or network traffic analyzers to capture and analyze POST requests to add.php. For example, using curl or wget to send crafted requests and observe the response can help verify if the system is vulnerable.
- Use curl to send a test POST request with a script payload in ticket_id: curl -X POST -d "ticket_id=<script>alert('XSS')</script>" https://yourserver/add.php -v
- Use grep or similar tools on web server logs to search for suspicious ticket_id values containing script tags or JavaScript code.
- Employ web vulnerability scanners that support detection of reflected XSS vulnerabilities targeting POST parameters.
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to upgrade Open ISES Tickets to version 3.44.2 or later, where this vulnerability has been patched.
The patch addresses the reflected XSS vulnerability by properly sanitizing the ticket_id POST parameter to prevent injection of arbitrary JavaScript.
If upgrading immediately is not possible, consider implementing input validation and output encoding on the ticket_id parameter to neutralize any malicious scripts.
Additionally, restrict access to the add.php endpoint to authenticated and trusted users only, as the vulnerability requires authentication.
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, which executes in the victim's browser. Such vulnerabilities can lead to unauthorized access to user data or session hijacking.
While the provided information does not explicitly mention compliance with standards like GDPR or HIPAA, XSS vulnerabilities generally pose risks to data confidentiality and integrity, which are critical aspects of these regulations.
If exploited, this vulnerability could potentially lead to unauthorized disclosure or manipulation of personal or sensitive data, thereby impacting compliance with data protection regulations that require safeguarding user information.
However, no direct statements or assessments regarding compliance impact are provided in the available resources.