CVE-2026-26890
Received Received - Intake
SQL Injection in Sourcecodester Pharmacy POS manage_product.php

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_product.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-26890
EUVD
EUVD-2026-9307
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_product.php. This vulnerability occurs in the URL parameter 'id', which is not properly sanitized. An attacker can inject malicious SQL code through this parameter, such as using a UNION-based SQL injection payload to retrieve sensitive information from the database, like the SQLite version."}, {'type': 'paragraph', 'content': 'This means that an attacker can manipulate the SQL queries executed by the application, potentially accessing unauthorized data or compromising the database.'}] [1]

Impact Analysis

This SQL injection vulnerability can allow attackers to execute arbitrary SQL commands on the database. This can lead to unauthorized data leakage, modification, or deletion of data, and potentially compromise the integrity and confidentiality of the application’s database.

Such an attack could result in exposure of sensitive information, disruption of service, or further exploitation of the 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_product.php?id=` for SQL injection payloads.'}, {'type': 'paragraph', 'content': 'A common detection method is to send a specially crafted HTTP request that attempts to inject SQL code and observe the response for database errors or unexpected data.'}, {'type': 'list_item', 'content': 'Use a curl command to test the injection point, for example: curl -i "http://<target>/pharmacy/manage_product.php?id=1\' union select 1, sqlite_version(), 3, 4, 5, 6, 7--+"'}, {'type': 'list_item', 'content': 'Look for the SQLite version or other database information in the HTTP response, which indicates successful injection.'}] [1]

Mitigation Strategies

I don't know

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