CVE-2026-26887
Received Received - Intake
SQL Injection in Sourcecodester Pharmacy POS manage_supplier.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_supplier.php.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-03
Last Modified
2026-03-04
Generated
2026-05-07
AI Q&A
2026-03-03
EPSS Evaluated
2026-05-05
NVD
EUVD
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 Powered Q&A
Can you explain this vulnerability to me?

The vulnerability is an SQL Injection found in Sourcecodester Pharmacy Point of Sale System v1.0, specifically in the file `/pharmacy/manage_supplier.php` at the URL parameter `id`.

An attacker can exploit this by injecting malicious SQL code through the `id` parameter, such as using a UNION-based SQL injection payload to retrieve sensitive information from the database, like the SQLite version.

This means the system does not properly sanitize or validate user input in this parameter, allowing unauthorized database queries to be executed.


How can this vulnerability impact me? :

This SQL Injection vulnerability can allow an attacker to access unauthorized data from the database, potentially exposing sensitive information.

The attacker could retrieve confidential data, manipulate database contents, or perform other malicious actions depending on the database privileges.

Such unauthorized access can lead to data breaches, loss of data integrity, and compromise of the overall system security.


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': 'This SQL Injection vulnerability can be detected by testing the `id` parameter in the `/pharmacy/manage_supplier.php` endpoint for injection flaws.'}, {'type': 'paragraph', 'content': 'A common detection method is to send a specially crafted HTTP request with a payload that attempts to manipulate the SQL query, such as using a UNION-based injection.'}, {'type': 'list_item', 'content': "Example payload to test: `/pharmacy/manage_supplier.php?id=-3' union select 1, sqlite_version(), 3--+`"}, {'type': 'paragraph', 'content': 'You can use tools like curl or a web proxy to send this request and observe if the response contains unexpected database information (e.g., SQLite version), indicating a successful injection.'}, {'type': 'list_item', 'content': "Example curl command: `curl -i 'http://<target>/pharmacy/manage_supplier.php?id=-3'%20union%20select%201,%20sqlite_version(),%203--+`"}] [1]


What immediate steps should I take to mitigate this vulnerability?

I don't know


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart