CVE-2023-36337
BaseFortify
Publication date: 2025-12-15
Last updated on: 2025-12-16
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| stemword | php_inventory_management_system | 1 |
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-2023-36337 is a reflected Cross-Site Scripting (XSS) vulnerability in the PHP Inventory Management System version 1, specifically in the /index.php/cuzh4 component. The application improperly handles user input by reflecting unsanitized URL parameters directly into the HTML output. This allows attackers to inject and execute arbitrary JavaScript code in the victim's browser by crafting malicious URLs. [1]
How can this vulnerability impact me? :
Successful exploitation of this vulnerability can allow attackers to perform session hijacking, steal user credentials, manipulate the user interface, and carry out unauthorized actions on behalf of the victim. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /index.php/cuzh4 endpoint of the PHP Inventory Management System for reflected XSS by injecting a crafted payload into the URL parameters. For example, accessing a URL like `http://localhost/php-inventory-management-system/index.php/cuzh4"><script>alert('XSS')</script>rvhmf` and observing if the script executes in the browser confirms the presence of the vulnerability. Automated tools like curl or browser-based testing can be used to send such requests and check for script execution. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include sanitizing and validating all user inputs on the /index.php/cuzh4 component to prevent injection of malicious scripts. Applying patches or updates provided by the vendor, if available, is recommended. Additionally, implementing Content Security Policy (CSP) headers can help reduce the impact of XSS attacks. If no patch is available, restricting access to the vulnerable endpoint or disabling it temporarily can reduce risk. [1]