CVE-2026-30563
Stored XSS in SourceCodester Sales Inventory update_details.php
Publication date: 2026-03-30
Last updated on: 2026-04-01
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ahsanriaz26gmailcom | sales_and_inventory_system | 1.0 |
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-30563 is a Stored Cross-Site Scripting (XSS) vulnerability found in SourceCodester Sales and Inventory System version 1.0, specifically in the update_details.php file.
The vulnerability occurs because the application does not properly sanitize the "website" parameter submitted via a POST request when updating store details.
An authenticated attacker can exploit this by injecting arbitrary JavaScript or HTML code into the "website" input field. This malicious code is then stored in the system's database and executed persistently whenever the store details page is accessed by any user or administrator.
How can this vulnerability impact me? :
This vulnerability can lead to persistent XSS attacks, where malicious scripts run every time the affected page is viewed.
- Attackers can hijack administrator sessions by stealing session cookies.
- Attackers can deface the settings page by altering its appearance using injected scripts.
- It can lead to unauthorized actions performed in the context of an authenticated user.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by attempting to inject a crafted XSS payload into the "website" parameter on the update_details.php page of the SourceCodester Inventory System version 1.0. Specifically, an authenticated user should log in as an administrator, navigate to the "Store Setting" or "Update Details" page, and submit a POST request with a malicious script in the "website" input field.
A proof-of-concept payload to test is: ```html "> <script>alert(123654);</script> ```
If the script executes (for example, an alert box with the number 123654 appears) when the store details page is accessed, the vulnerability is present.
To detect this via command line, you can use tools like curl to send a crafted POST request:
- curl -X POST -d "website=\"> <script>alert(123654);</script>" https://[target]/update_details.php --cookie "[admin_session_cookie]"
Replace [target] with the target URL and [admin_session_cookie] with a valid administrator session cookie to authenticate the request.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include sanitizing and validating the "website" parameter input on the update_details.php page to prevent injection of arbitrary scripts.
Ensure that all user inputs, especially those submitted via POST requests, are properly escaped or filtered to remove or encode HTML and JavaScript content.
Restrict access to the update_details.php functionality to only trusted and authenticated users.
As a temporary workaround, consider disabling or restricting the "Update Store Details" feature until a patch or update is applied.
Monitor the application for any suspicious activity or unexpected script execution on the store details page.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The Stored Cross-Site Scripting (XSS) vulnerability in SourceCodester Sales and Inventory System 1.0 allows attackers to inject and execute arbitrary scripts, which can lead to session hijacking and unauthorized access to administrator accounts.
Such unauthorized access and potential data breaches can compromise the confidentiality and integrity of sensitive information, thereby negatively impacting compliance with common standards and regulations like GDPR and HIPAA that require protection of personal and sensitive data.
Specifically, failure to properly sanitize input and prevent persistent XSS attacks can result in exposure of user data, unauthorized data manipulation, and loss of control over protected information, all of which are critical compliance concerns under these regulations.