Skip to main content
VulnerabilityPublished Updated

CVE-2026-26708: Sale System · SQL Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 27% 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-26708, organizations should implement the following specific actions: 1) Immediately restrict access to the /pharmacy/manage_user.php endpoint using network segmentation, firewalls, or application-layer access controls to limit exposure. 2) Conduct a thorough code review of the affected script to identify and sanitize all user inputs, employing parameterized queries or prepared statements to prevent SQL Injection. 3) If possible, apply any vendor-provided patches or updates as soon as they become available; in their absence, consider temporary workarounds such as disabling vulnerable functionality. 4) Implement Web Application Firewalls (WAFs) with custom rules to detect and block SQL Injection payloads targeting this endpoint. 5) Monitor database logs and application logs for unusual query patterns or errors indicative of injection attempts. 6) Educate developers and administrators on secure coding practices and the importance of input validation. 7) Regularly back up critical data and test restoration procedures to minimize impact in case of data corruption. 8) Consider deploying intrusion detection systems (IDS) tuned for SQL Injection signatures. These measures, combined, will reduce the risk of exploitation and limit potential damage.

Description

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

References

Community reviews

Loading reviews…