What is the CVSS score of CVE-2026-26707?

CVE-2026-26707 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.0%.

Is there a public PoC exploit available for CVE-2026-26707?

Yes, a public proof-of-concept exploit is available for CVE-2026-26707. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2026-26707?

Within 24 hours: Isolate affected Pharmacy POS systems from production networks and disable public internet access to /pharmacy/view_supplier.php. Within 7 days: Implement Web Application Firewall (WAF) rules to block SQL injection patterns on this endpoint, apply input validation patches if available from sourcecodester, and conduct database access log review for signs of exploitation. Within 30 days: Plan migration to a patched version or alternative POS solution, complete comprehensive security assessment of the application, and establish vendor security update monitoring processes.

Pharmacy Point Of Sale System CVE-2026-26707

CRITICAL

SQL Injection (CWE-89)

2026-03-02 cve@mitre.org

PHP SQLi Pharmacy Point Of Sale System Oretnom23

9.8

CVSS 3.1 · NVD

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Send crafted SQL query in supplier parameter
Exploit

Bypass authentication checks
Execution

Extract sensitive database records
Impact

Modify or delete pharmacy data

Vulnerability Assessment

Weakness	CWE CWE-89 OWASP Top 10:2025 A05:2025 - Injection ASVS 5.0 V1 - Encoding and Sanitization Parameterized queries, prepared statements MITRE ATT&CK 2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. Sign in to read
Exploitation Conditions	No special conditions — remote unauthenticated exploitation against default Pharmacy Point of Sale System v1.0 installations accessible via /pharmacy/view_supplier.php endpoint.
Impact	CVSS 9.8.
Exploit ScenarioDerived	SQL injection.

Act Now Prioritize within 24-48h. Why: CRITICAL severity + public POC available.

No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

Pharmacy POS has a fifth SQL injection in view_sales.

Earlier versions of this analysis (1)

v1 Mar 12, 2026 - 21:55 CVSS 9.8

Fifth pharmacy POS SQLi.

RemediationAI

Do not deploy.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

CWE-89.

Know when Pharmacy Point Of Sale System gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 9.8 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

PoC Detected

Mar 03, 2026 - 21:15 vuln.today

Public exploit code

CVE Published

Mar 02, 2026 - 18:16 nvd

CRITICAL 9.8

DescriptionCVE.org

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

Executive ViewAI

Why It Matters

A critical SQL injection vulnerability in our Pharmacy Point of Sale System (v1.0) allows unauthenticated attackers to access, modify, or delete pharmacy data including patient records and inventory. This vulnerability is actively being exploited in the wild and poses an immediate risk to patient privacy, regulatory compliance, and operational continuity.

Business Impact: Severe

Compensating Controls

Implement WAF rules to detect and block SQL injection payloads targeting /pharmacy/view_supplier.php; restrict network access to this endpoint via firewall (whitelist only authorized internal IPs); disable the supplier view feature if operationally feasible; apply input validation and parameterized query patches if available from sourcecodester; monitor database logs for suspicious queries; consider running application on isolated network segment with restricted database permissions.

Threat Intelligence Overview

EPSS Score

0.0%

Top 89% exploitable

Exploit

POC

Public exploit code exists

Data Quality

4 sources

Confidence: Medium

NVD

CVE.org

EPSS

GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity CRITICAL

CISA KEV No

Public POC Yes

EPSS 0.0%

Patch available No

Active threat No

Deciding rule

CRITICAL severity + public POC available

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.