CVE-2026-26706
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedsourcecodester Pharmacy Point of Sale System v1.0 is vulnerable to SQL Injection in /pharmacy/view_receipt.php.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Pharmacy Point of Sale System v1.0 by SourceCodester contains a SQL Injection vulnerability in the view_receipt.php file. This allows remote attackers to inject malicious SQL commands through unsanitized input, potentially enabling unauthorized database access, data exfiltration, or complete system compromise. The critical CVSS score of 9.8 indicates the vulnerability is exploitable over the network with low complexity and no authentication required.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed version of Pharmacy Point of Sale SystemLocate the application directory and check for version indicators such as a version file, footer/version in source code, or any README/installation files. Compare against version 1.0.Affected if The application version is exactly 1.0 and is the Oretnom23 Pharmacy Point Of Sale System.
-
Verify presence of vulnerable file view_receipt.phpCheck for the existence of /pharmacy/view_receipt.php within the web application root directory.Affected if The file /pharmacy/view_receipt.php exists in the application.
-
Confirm the application is accessible over networkAttempt to access the application's login page or main interface via HTTP/HTTPS to confirm the system is deployed and reachable.Affected if The Pharmacy POS System is deployed and accessible (not just source code installed).
-
Identify if user-supplied input reaches the vulnerable scriptReview view_receipt.php for direct use of request parameters (GET/POST) in SQL queries without visible sanitization or parameterized query implementation.Affected if The script accepts user input (via query parameters or form data) and uses it directly in SQL queries without prepared statements or input validation.
The system is affected if it runs Oretnom23 Pharmacy Point of Sale System v1.0 with the view_receipt.php file accessible and using unsanitized user input in SQL queries.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRemediate by replacing dynamic SQL queries with parameterized statements or prepared statements in view_receipt.php, and conduct a broader code audit to identify and fix similar SQL injection vulnerabilities throughout the application.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26706 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-26706 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data