CVE-2026-26705
SQL Injection in Pharmacy POS System /view_product.php
Publication date: 2026-03-02
Last updated on: 2026-03-03
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| oretnom23 | pharmacy_point_of_sale_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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?
The vulnerability in sourcecodester Pharmacy Point of Sale System v1.0 is an SQL Injection found in the /pharmacy/view_product.php file.
SQL Injection is a security flaw that allows an attacker to interfere with the queries that an application makes to its database. This can enable the attacker to view, modify, or delete data they are not normally able to access.
How can this vulnerability impact me? :
This SQL Injection vulnerability can allow an attacker to access sensitive information stored in the database, such as product details or potentially user data.
It may also allow the attacker to modify or delete data, which can disrupt the normal operation of the Pharmacy Point of Sale System.
Overall, this can lead to data breaches, loss of data integrity, and operational downtime.
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': 'The vulnerability is an SQL Injection in /pharmacy/view_product.php of the sourcecodester Pharmacy Point of Sale System v1.0. Detection typically involves sending crafted input to the vulnerable parameter and observing the response for SQL errors or unexpected behavior.'}, {'type': 'paragraph', 'content': 'Common commands to detect SQL Injection include using tools like sqlmap or manual testing with payloads such as "\' OR \'1\'=\'1" in the URL or POST parameters targeting /pharmacy/view_product.php.'}, {'type': 'list_item', 'content': 'Example manual test: curl "http://target/pharmacy/view_product.php?id=1\' OR \'1\'=\'1"'}, {'type': 'list_item', 'content': 'Using sqlmap: sqlmap -u "http://target/pharmacy/view_product.php?id=1" --batch'}] [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include validating and sanitizing all user inputs to prevent malicious SQL code execution.
Use prepared statements or parameterized queries in the application code to avoid direct concatenation of user input into SQL queries.
If possible, restrict database user permissions to limit the impact of a successful injection.
Additionally, monitor logs for suspicious activity and consider applying any available patches or updates from the vendor.