CVE-2026-48230
Deferred Deferred - Pending Action
Reflected XSS in Open ISES Tickets before 3.44.2

Publication date: 2026-05-21

Last updated on: 2026-05-21

Assigner: VulnCheck

Description
Open ISES Tickets before 3.44.2 contains a reflected cross-site scripting vulnerability in ticketsmdb_import.php that allows authenticated attackers to inject arbitrary JavaScript by passing an unsanitized value through the multiple POST parameters (mdbhost, mdbdb, mdbuser, mdbpassword, mdbprefix, ticketshost, ticketsdb, ticketsuser, ticketspassword, ticketsprefix) directly into HTML form hidden input value attributes. Attackers can craft a malicious request containing a JavaScript payload that executes in the victim's browser when the response is rendered.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-21
Last Modified
2026-05-21
Generated
2026-05-22
AI Q&A
2026-05-21
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
openises tickets 3.44.2
openises tickets to 3.44.2 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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?

This vulnerability is a reflected cross-site scripting (XSS) issue found in Open ISES Tickets versions before 3.44.2. It occurs in the file ticketsmdb_import.php, where multiple POST parameters (such as mdbhost, mdbdb, mdbuser, mdbpassword, mdbprefix, ticketshost, ticketsdb, ticketsuser, ticketspassword, ticketsprefix) are not properly sanitized before being inserted into HTML form hidden input value attributes. An authenticated attacker can exploit this by injecting arbitrary JavaScript code through these parameters, which then executes in the victim's browser when the response is rendered.


How can this vulnerability impact me? :

This vulnerability can allow an attacker to execute arbitrary JavaScript in the context of a victim's browser session. This can lead to various impacts such as theft of sensitive information (like session cookies), performing actions on behalf of the victim, or delivering malicious payloads. Since the attacker must be authenticated, the risk is limited to users with access, but it still poses a significant security threat.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability is a reflected cross-site scripting (XSS) issue that allows authenticated attackers to inject arbitrary JavaScript into the application. Such vulnerabilities can lead to unauthorized access to user data or session hijacking, which may result in breaches of confidentiality and integrity.

While the provided context 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 could lead to exposure of personal or sensitive information, potentially causing non-compliance with such standards.

The fixed version 3.44.2 addresses multiple security issues including XSS vulnerabilities, which helps improve the security posture and reduce risks related to regulatory compliance.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

The vulnerability involves reflected cross-site scripting (XSS) in multiple POST parameters of ticketsmdb_import.php. Detection would involve monitoring HTTP POST requests to this endpoint for suspicious or unexpected JavaScript payloads in parameters such as mdbhost, mdbdb, mdbuser, mdbpassword, mdbprefix, ticketshost, ticketsdb, ticketsuser, ticketspassword, and ticketsprefix.

You can detect attempts by capturing and inspecting HTTP traffic to the affected application, looking for POST requests with suspicious script tags or JavaScript code in these parameters.

Example commands to detect such attempts might include using network traffic analysis tools like tcpdump or tshark to filter HTTP POST requests to ticketsmdb_import.php, for example:

  • tcpdump -A -s 0 'tcp port 80 and (((ip[2:2] - ((ip[0]&0xf)<<2)) - ((tcp[12]&0xf0)>>2)) != 0)' | grep 'POST /ticketsmdb_import.php'
  • tshark -Y 'http.request.method == "POST" and http.request.uri contains "ticketsmdb_import.php"' -T fields -e http.file_data

Additionally, web application firewalls (WAFs) or intrusion detection systems (IDS) can be configured to alert on suspicious input patterns in these POST parameters.


What immediate steps should I take to mitigate this vulnerability?

The primary mitigation is to upgrade the openises/tickets software to version 3.44.2 or later, which includes fixes for this and many other vulnerabilities.

Version 3.44.2 patches multiple reflected XSS vulnerabilities by properly sanitizing user inputs using functions like htmlspecialchars() and intval(), preventing injection of malicious JavaScript.

If immediate upgrade is not possible, consider implementing input validation and sanitization on the server side for the affected POST parameters, and deploying a web application firewall (WAF) to block suspicious payloads.

Also, review and restrict access to the ticketsmdb_import.php endpoint to authenticated and trusted users only, as the vulnerability requires authentication.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart