CVE-2026-26888
SQL Injection in Sourcecodester Pharmacy POS Manage_Stock.php
Publication date: 2026-03-03
Last updated on: 2026-03-04
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
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2026-26888 is an SQL injection vulnerability found in Sourcecodester Pharmacy Point of Sale System v1.0, specifically in the file /pharmacy/manage_stock.php.'}, {'type': 'paragraph', 'content': "The vulnerability occurs because the 'id' parameter in the URL is not properly sanitized, allowing an attacker to inject arbitrary SQL code."}, {'type': 'paragraph', 'content': 'An example attack uses a UNION SELECT statement to retrieve information such as the SQLite database version, demonstrating that the backend database is SQLite.'}, {'type': 'paragraph', 'content': 'This flaw enables attackers to execute unauthorized SQL queries on the system.'}] [1]
How can this vulnerability impact me? :
This SQL injection vulnerability can allow attackers to execute unauthorized SQL commands, which may lead to data leakage or unauthorized access to sensitive information stored in the database.
Attackers could potentially manipulate or retrieve confidential data, compromise the integrity of the system, or escalate their access privileges.
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 /pharmacy/manage_stock.php endpoint with specially crafted SQL injection payloads in the id parameter.'}, {'type': 'paragraph', 'content': "A common detection method is to send a GET request with an SQL injection payload such as: /pharmacy/manage_stock.php?id=5' union select 1,2,3,4,sqlite_version(),6--+"}, {'type': 'paragraph', 'content': 'If the response reveals database information (like the SQLite version), it confirms the presence of the SQL injection vulnerability.'}, {'type': 'paragraph', 'content': 'You can use command-line tools like curl to test this, for example:'}, {'type': 'list_item', 'content': 'curl "http://<target-host>/pharmacy/manage_stock.php?id=5\'%20union%20select%201,2,3,4,sqlite_version(),6--+"'}, {'type': 'paragraph', 'content': 'Analyzing the response for database version or error messages indicating SQL injection can help confirm the vulnerability.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
I don't know