CVE-2026-90694
Received Received - Intake

Cross-Site Scripting in Inventory Management System 1.0

Publication date: 2026-09-14

Last updated on: 2026-09-14

Assigner: VulDB

Description
A vulnerability has been found in SourceCodester Inventory Management System 1.0. Affected is an unknown function of the file /api/customers_handler.php of the component Customer Management Module. Such manipulation of the argument Customer_Name leads to cross site scripting. The attack can be executed remotely. The exploit has been disclosed to the public and may be used.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-14
Last Modified
2026-09-14
Generated
2026-09-14
AI Q&A
2026-09-14
EPSS Evaluated
N/A
NVD
CVE-2026-90694
EUVD
EUVD-2026-77319

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
sourcecodester inventory_management_system 1.0

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.
CWE-94 The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a stored Cross-Site Scripting (XSS) vulnerability in the Inventory Management System 1.0. It allows an attacker to inject malicious JavaScript into the Customer Name field via the /api/customers_handler.php file. The injected script is stored in the database and executed when users view the Customer List page, potentially enabling session hijacking or account takeover.

Detection Guidance

To detect this XSS vulnerability, inspect the Customer Management module in Inventory Management System 1.0. Check if user input in the Customer Name field is stored without sanitization. Review the /api/customers_handler.php and /customers.php files for improper handling of input. Test by injecting a harmless script like <script>alert(1)</script> into the Customer Name field and verify if it executes when viewing the Customer List page.

Commands to check for vulnerable endpoints: curl -X POST http://<target>/api/customers_handler.php -d 'Customer_Name=<script>alert(1)</script>' and then curl http://<target>/customers.php to see if the script executes.

Impact Analysis

An attacker could steal user sessions, take over accounts, or perform actions on behalf of users. This could lead to unauthorized access to sensitive data, manipulation of customer information, or further compromise of the system.

Compliance Impact

This vulnerability could violate GDPR by exposing personal data through session hijacking or account takeover. For HIPAA, it may compromise protected health information if customer data includes such details. Both standards require protection against unauthorized access and data breaches.

Mitigation Strategies

Apply htmlspecialchars() to user-supplied data in the Customer Name field before storing it in the database. Implement server-side input validation to reject or sanitize special characters. Use Content Security Policy (CSP) headers to restrict script execution. Apply parameterized output encoding when rendering data in the browser.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-90694. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart