CVE-2026-8083
Deferred Deferred - Pending Action
SQL Injection in Pharmacy Sales and Inventory System

Publication date: 2026-05-07

Last updated on: 2026-05-07

Assigner: VulDB

Description
A vulnerability was found in SourceCodester Pharmacy Sales and Inventory System 1.0. This affects an unknown part of the file /ajax.php?action=save_user. The manipulation of the argument ID results in sql injection. The attack can be executed remotely. The exploit has been made public and could be used.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-07
Last Modified
2026-05-07
Generated
2026-05-09
AI Q&A
2026-05-07
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
sourcecodester pharmacy_sales_and_inventory_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.
CWE-74 The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is a SQL injection found in the Pharmacy Sales and Inventory System version 1.0, specifically in the file /ajax.php?action=save_user. It occurs due to improper input validation of the 'id' parameter, which allows an attacker to inject malicious SQL queries remotely without authentication.

The vulnerability is classified as a boolean-based blind SQL injection, meaning attackers can manipulate database queries to extract or alter data by sending crafted inputs and observing the system's responses.


How can this vulnerability impact me? :

Exploitation of this vulnerability can lead to unauthorized access to the database, allowing attackers to view, modify, or delete sensitive information.

It can result in data manipulation, leakage of confidential data, and potentially full system compromise.

Since the attack can be executed remotely without authentication, it poses a significant security risk to affected systems.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability is a boolean-based blind SQL injection in the /ajax.php?action=save_user endpoint, specifically in the id parameter. It can be detected by testing this parameter for SQL injection vulnerabilities.

One common method to detect this vulnerability is to use automated tools like sqlmap, which can test and exploit SQL injection points.

  • Use sqlmap with a command such as: sqlmap -u "http://target/ajax.php?action=save_user&id=1" --batch
  • Manually test by injecting SQL payloads into the id parameter and observing responses, for example by appending ' or 1=1-- to the id value.

What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include applying strict input validation on the id parameter to prevent malicious SQL code from being executed.

Use prepared statements or parameterized queries in the code handling the id parameter to avoid SQL injection.

Minimize database user permissions to limit the impact of a potential exploit.

Conduct regular security audits and update the software to a patched version once available.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The SQL injection vulnerability in the Pharmacy Sales and Inventory System allows unauthorized database access and potential leakage of sensitive information. Such unauthorized access and data breaches can lead to non-compliance with data protection regulations like GDPR and HIPAA, which mandate the protection of personal and sensitive data.

Failure to secure the system against this vulnerability could result in exposure of personal health information or other sensitive data, thereby violating confidentiality and integrity requirements stipulated by these standards.


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