Skip to main content
VulnerabilityPublished Updated

CVE-2026-26706: Sale System · SQL Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

To mitigate CVE-2026-26706, organizations should immediately audit the /pharmacy/view_receipt.php code to identify and remediate unsafe SQL query constructions. Implement parameterized queries or prepared statements to prevent injection of malicious SQL code. Employ rigorous input validation and sanitization on all user-supplied data, especially parameters used in database queries. Restrict database user permissions to the minimum necessary to limit the impact of potential exploitation. Monitor database logs and application logs for unusual query patterns or errors indicative of injection attempts. If possible, isolate the affected system from direct internet exposure and enforce network segmentation. Regularly back up databases to enable recovery in case of data tampering or loss. Engage with the software vendor or community to obtain patches or updates addressing this vulnerability. Consider deploying Web Application Firewalls (WAFs) with SQL Injection detection rules as an additional protective layer. Finally, conduct security awareness training for developers and administrators on secure coding practices to prevent similar vulnerabilities.

Description

sourcecodester Pharmacy Point of Sale System v1.0 is vulnerable to SQL Injection in /pharmacy/view_receipt.php.

References

Community reviews

Loading reviews…