MEDIUM 4.3

CVE-2026-13554: XSS in itsourcecode Hotel Management System Admin Panel

A stored cross-site scripting (XSS) vulnerability exists in itsourcecode Online Hotel Management System version 1.0. An attacker can inject malicious JavaScript code through the amenities management interface that executes in the browsers of other users—specifically administrators—when they view the poisoned data. The vulnerability requires user interaction (clicking a link or viewing a page with the payload) but no authentication to create the malicious input.

Source data · NVD / CISA · public domain

CVSS
3.1 · 4.3 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Weaknesses (CWE)
CWE-79, CWE-94
Affected products
0 configuration(s)
Published / Modified
2026-06-29 / 2026-06-30

NVD description (verbatim)

A vulnerability has been found in itsourcecode Online Hotel Management System 1.0. Affected by this vulnerability is an unknown functionality of the file /admin/mod_amenities/controller.php?action=add of the component POST Request Handler. The manipulation of the argument Name leads to cross site scripting. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

6 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-13554 is a reflected or stored XSS flaw in the POST request handler for /admin/mod_amenities/controller.php with the action parameter set to 'add'. The 'Name' parameter fails to properly sanitize or encode user-supplied input before rendering it in the administrative interface. The vulnerability maps to CWE-79 (Improper Neutralization of Input During Web Page Generation) and CWE-94 (Improper Control of Generation of Code), indicating both direct output encoding failures and potential downstream code execution risks. The CVSS 3.1 score of 4.3 (MEDIUM) reflects network accessibility, low attack complexity, and lack of privileges required, offset by the requirement for user interaction and limited confidentiality impact.

Business impact

An attacker leveraging this vulnerability could deface administrative interfaces, steal session cookies or authentication tokens from hotel management staff, perform unauthorized actions on the system, or redirect administrators to malicious sites. In a hotel context, this could lead to manipulation of guest data, booking records, or payment information visible to administrators. The public disclosure status means active exploitation is plausible, increasing the window of risk for unpatched instances.

Affected systems

itsourcecode Online Hotel Management System version 1.0 is confirmed vulnerable. Administrators and staff with access to the /admin/mod_amenities/controller.php endpoint are direct targets. Any browser accessing the vulnerable admin panel while logged in or viewing administrator-shared links could execute the injected script.

Exploitability

The exploit has been publicly disclosed, lowering the barrier to weaponization. The attack requires no authentication to craft the malicious payload (unauthenticated submission to the add amenities action), but does require a user (typically an admin) to interact with the injected data by viewing or navigating to a page containing it. This combination—easy payload delivery plus user interaction requirement—makes it moderately exploitable in practice, particularly if administrators are social engineered into clicking malicious links.

Remediation

Immediately apply any available patches from itsourcecode for version 1.0. If patches are unavailable, implement input validation to reject or strip suspicious characters from the Name parameter, and deploy output encoding (HTML entity encoding) for all user-supplied data displayed in the admin interface. Consider restricting access to the admin panel by IP whitelist or network segmentation. A Web Application Firewall (WAF) with XSS detection rules can provide interim protection.

Patch guidance

Contact itsourcecode directly to verify if a patched version exists for the Online Hotel Management System 1.0 branch. Given the public disclosure date of 2026-06-29, prioritize obtaining vendor guidance within days, not weeks. If no patch is forthcoming from the vendor, evaluate alternative hotel management software or implement the compensating controls outlined in the remediation summary.

Detection guidance

Monitor access logs for POST requests to /admin/mod_amenities/controller.php?action=add containing HTML or JavaScript-like syntax in the Name parameter (e.g., <script>, onerror=, onload=, etc.). Implement Content Security Policy (CSP) headers in the admin panel to restrict inline script execution. Use browser developer tools or automated scanning to identify stored XSS vectors in the amenities database. Log and alert on anomalous administrative activity, such as unexpected redirects or session hijacking indicators.

Why prioritize this

Although the CVSS score is MEDIUM (4.3), prioritize patching because: (1) the exploit is publicly available, increasing active threat likelihood; (2) the vulnerability affects administrative interfaces where trusted users operate, making the impact of successful exploitation disproportionately severe; (3) hotel systems often handle payment and personal guest information, elevating downstream business risk; (4) no KEV listing or immediate indicators of active ransomware exploitation should not lower vigilance, given the disclosure timeline.

Risk score, explained

The CVSS 3.1 score of 4.3 reflects a network-accessible vulnerability (AV:N) with low attack complexity (AC:L), requiring no privileges (PR:N) but user interaction (UI:R). The scope is unchanged (S:U), and impact is limited to integrity (I:L) with no confidentiality or availability impact. This scoring is appropriate for a reflected/stored XSS requiring a victim to view the malicious content; the score would be higher if the vulnerability allowed unauthenticated privilege escalation or data exfiltration. The MEDIUM rating appropriately captures that while the attack surface is broad and initial compromise is achievable, the immediate harm is constrained to session hijacking or minor data manipulation rather than system takeover.

Frequently asked questions

Can this vulnerability be exploited without the victim clicking a link?

Depends on whether the XSS is stored (persistent) or reflected. If stored in the amenities database, any admin viewing the amenities list automatically executes the payload without clicking. If reflected, the attacker must trick a user into clicking a malicious link. Either way, the payload executes in the admin's browser. Verify with your vendor whether the vulnerable parameter stores data persistently.

Do I need to be logged in as an admin to exploit this?

No. The vulnerability allows unauthenticated submission of the malicious Name parameter to the add amenities endpoint. However, execution of the payload occurs when an authenticated admin views the resulting data. The asymmetry—easy injection, high-privilege execution—is what makes XSS particularly dangerous in admin interfaces.

What should I do if I cannot patch immediately?

Implement output encoding (HTML entity encoding) on all user-supplied fields displayed in the admin UI. Apply a Web Application Firewall rule to block requests containing script tags or event handlers in the Name parameter. Restrict administrative access by IP whitelist or VPN. Monitor for suspicious admin activity and session anomalies. Escalate vendor contact for patch timelines.

Is this in the CISA KEV catalog?

No, this vulnerability is not currently listed in the CISA Known Exploited Vulnerabilities catalog as of the modification date. However, public disclosure does not require KEV listing to pose a genuine threat. Treat it as exploitable and prioritize accordingly.

This analysis is based on publicly available vulnerability data current as of 2026-06-30. Patch versions, vendor status, and remediation timelines should be verified directly with itsourcecode. No exploit code or proof-of-concept is provided. Organizations should conduct their own risk assessments based on deployment context, data sensitivity, and network exposure. SEC.co makes no warranty regarding the completeness or timeliness of this information. Source: NVD (public-domain), retrieved 2026-08-08. Analysis generated by SEC.co (claude-haiku-4-5).