CVE-2026-3753
Received Received - Intake
SQL Injection in SourceCodester Sales Inventory /add_sales_print.php

Publication date: 2026-03-08

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability has been found in SourceCodester Sales and Inventory System up to 1.0. The impacted element is an unknown function of the file /add_sales_print.php. Such manipulation of the argument sid leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-08
Last Modified
2026-04-29
Generated
2026-05-06
AI Q&A
2026-03-08
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
ahsanriaz26gmailcom sales_and_inventory_system 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-74 The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

[{'type': 'paragraph', 'content': "CVE-2026-3753 is a SQL Injection vulnerability found in SourceCodester Sales and Inventory System version 1.0, specifically in the file add_sales_print.php. The vulnerability occurs because the application does not properly sanitize the 'sid' parameter in HTTP GET requests, allowing attackers to inject malicious SQL code."}, {'type': 'paragraph', 'content': "An authenticated attacker can exploit this flaw by supplying specially crafted values to the 'sid' parameter, enabling various SQL injection techniques such as UNION-based, Boolean-based, and time-based blind SQL injections."}, {'type': 'paragraph', 'content': "This allows attackers to retrieve sensitive database information, enumerate database schema elements like tables and columns, and potentially compromise the confidentiality and integrity of the system's data."}] [1, 2, 3]


How can this vulnerability impact me? :

[{'type': 'paragraph', 'content': 'This vulnerability can have significant impacts including unauthorized access to sensitive data stored in the backend database.'}, {'type': 'paragraph', 'content': "Attackers can exfiltrate confidential information by injecting SQL commands through the vulnerable 'sid' parameter."}, {'type': 'paragraph', 'content': 'It can also lead to unauthorized modification or corruption of data, affecting the integrity of the system.'}, {'type': 'paragraph', 'content': 'Because the vulnerability can be exploited remotely and with relative ease, it poses a serious risk to the availability and trustworthiness of the affected system.'}] [1, 2, 3]


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

I don't know


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

[{'type': 'paragraph', 'content': "This vulnerability can be detected by testing the 'sid' parameter in HTTP GET requests to the add_sales_print.php file for SQL injection flaws."}, {'type': 'paragraph', 'content': 'One effective method is to use automated SQL injection testing tools such as sqlmap with a command like:'}, {'type': 'list_item', 'content': 'sqlmap -u "http://127.0.0.1:8089/add_sales_print.php?sid=SD425" --batch -v 6 --risk=3 --cookie "PHPSESSID=YOUR_COOKIE_HERE"'}, {'type': 'paragraph', 'content': "Additionally, manual testing can be performed by injecting payloads into the 'sid' parameter, including UNION-based, Boolean-based blind, and time-based blind SQL injection payloads to observe the system's response."}, {'type': 'list_item', 'content': "Example UNION-based payload: sid=SD425' UNION ALL SELECT NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,CONCAT(0x716a717171,0x50614e79737455716145634475617a6c585a57546a58504d6b78594e4f51735a5a4667684b475344,0x7171767871),NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL-- -"}, {'type': 'list_item', 'content': "Example Boolean-based blind payload: sid=SD425' AND 3136=3136 AND 'qqpq'='qqpq"}, {'type': 'list_item', 'content': "Example Time-based blind payload: sid=SD425' AND (SELECT 4276 FROM (SELECT(SLEEP(5)))moTn) AND 'POYW'='POYW"}] [1]


What immediate steps should I take to mitigate this vulnerability?

[{'type': 'paragraph', 'content': 'No known countermeasures or mitigations have been reported for this vulnerability.'}, {'type': 'paragraph', 'content': 'It is suggested to replace the affected component or product with an alternative that does not contain this vulnerability.'}, {'type': 'paragraph', 'content': "As an immediate step, restrict access to the vulnerable add_sales_print.php file and monitor for suspicious activity involving the 'sid' parameter."}, {'type': 'paragraph', 'content': "Additionally, applying web application firewall (WAF) rules to detect and block SQL injection attempts targeting the 'sid' parameter may help mitigate exploitation risks until a permanent fix is applied."}] [3]


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