CVE-2026-26706
SQL Injection in Pharmacy POS v1.0 /view_receipt.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_receipt.php file. This means that an attacker can manipulate the SQL queries executed by the application by injecting malicious SQL code through input fields or parameters, potentially gaining unauthorized access to the database or manipulating its contents.
How can this vulnerability impact me? :
This SQL Injection vulnerability can allow attackers to access sensitive information stored in the database, modify or delete data, and potentially compromise the integrity and confidentiality of the system. It may lead to unauthorized data disclosure, data loss, or further exploitation of the system.
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 the /pharmacy/view_receipt.php file of the sourcecodester Pharmacy Point of Sale System v1.0. Detection typically involves testing this endpoint for SQL Injection by injecting SQL syntax into input parameters and observing the response.'}, {'type': 'paragraph', 'content': 'Common commands to detect SQL Injection include using tools like sqlmap or manual testing with curl or browser-based requests by inserting SQL payloads such as "\' OR \'1\'=\'1" into parameters.'}, {'type': 'list_item', 'content': 'Example curl command to test for SQL Injection: curl -G "http://target/pharmacy/view_receipt.php" --data-urlencode "id=\' OR \'1\'=\'1"'}, {'type': 'list_item', 'content': 'Use sqlmap to automate detection: sqlmap -u "http://target/pharmacy/view_receipt.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 on the /pharmacy/view_receipt.php page 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 permissions to limit the impact of a successful injection.
Monitor and block suspicious requests targeting the vulnerable endpoint until a patch or update is applied.