CVE-2026-26889
Received Received - Intake
SQL Injection in Sourcecodester Pharmacy POS Category Management

Publication date: 2026-03-03

Last updated on: 2026-03-04

Assigner: MITRE

Description
Sourcecodester Pharmacy Point of Sale System v1.0 is vulnerable to SQL Injection in /pharmacy/manage_category.php.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-03
Last Modified
2026-03-04
Generated
2026-06-16
AI Q&A
2026-03-03
EPSS Evaluated
2026-06-15
NVD
CVE-2026-26889
EUVD
EUVD-2026-9306
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
oretnom23 pharmacy_point_of_sale_system 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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 Quick Actions
Instant insights powered by AI
Executive Summary

[{'type': 'paragraph', 'content': "The Pharmacy Point of Sale System v1.0 by Sourcecodester has an SQL injection vulnerability in the file /pharmacy/manage_category.php. This vulnerability occurs in the URL parameter 'id', where an attacker can inject malicious SQL code."}, {'type': 'paragraph', 'content': "For example, an attacker can use a payload like /pharmacy/manage_category.php?id=3' union select 1, sqlite_version(), 3, 4--+ to exploit this vulnerability. This allows the attacker to execute arbitrary SQL commands, such as retrieving the database version or other sensitive data."}] [1]

Impact Analysis

This SQL injection vulnerability can allow attackers to execute arbitrary SQL commands on the database, which may lead to unauthorized data access, data leakage, or modification of the database contents.

Such exploitation can compromise the integrity and confidentiality of the database, potentially exposing sensitive information stored within the Pharmacy Point of Sale System.

Compliance Impact

I don't know

Detection Guidance

[{'type': 'paragraph', 'content': 'This SQL injection vulnerability can be detected by testing the `id` parameter in the URL `/pharmacy/manage_category.php?id=` for SQL injection payloads.'}, {'type': 'paragraph', 'content': 'A common detection method is to send a crafted HTTP request with a UNION-based SQL injection payload to see if the database responds with unexpected data.'}, {'type': 'paragraph', 'content': 'For example, you can use curl to test the vulnerability with the following command:'}, {'type': 'list_item', 'content': 'curl "http://[target]/pharmacy/manage_category.php?id=3\' union select 1, sqlite_version(), 3, 4--+" -H "Cookie: PHPSESSID=[session_id]"'}, {'type': 'paragraph', 'content': 'If the response contains the SQLite version or other unexpected data, it indicates the presence of the SQL injection vulnerability.'}] [1]

Mitigation Strategies

I don't know

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-26889. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart