CVE-2026-26705
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_product.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 confidenceSQL Injection vulnerability in sourcecodester Pharmacy Point of Sale System v1.0 at /pharmacy/view_product.php allows remote attackers to inject arbitrary SQL commands via unsanitized input parameters, potentially enabling data exfiltration, authentication bypass, or complete database compromise.
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.
-
Confirm Pharmacy POS installationLocate the web application directory and identify if the Pharmacy Point of Sale System by Oretnom23 is installed. Check for the presence of /pharmacy/ directory or related application files.Affected if The Oretnom23 Pharmacy Point of Sale System is installed on the server.
-
Identify installed versionInspect application files for version information, typically found in README files, config files, or the main index.php. Compare the discovered version against version 1.0.Affected if The installed version is exactly 1.0 (Oretnom23 Pharmacy Point Of Sale System v1.0).
-
Locate vulnerable fileCheck for the presence of /pharmacy/view_product.php in the web root directory.Affected if The file view_product.php exists in the pharmacy directory.
-
Inspect SQL query handlingOpen view_product.php and examine database query code. Look for SQL statements that incorporate user input without using prepared statements, parameterized queries, or proper escaping.Affected if The file contains SQL queries that directly use request parameters without sanitization or parameter binding.
-
Verify database connectivityConfirm the application is configured to connect to a MySQL or other database server. Check configuration files for database credentials and connection settings.Affected if The application connects to a database and the vulnerable SQL code is executable.
The system is affected if it runs Oretnom23 Pharmacy Point of Sale System version 1.0 with the vulnerable view_product.php file containing unsanitized SQL queries accessible to remote users.
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 dataImplement prepared statements/parameterized queries in view_product.php for all database operations, apply input validation and sanitization, and ensure the database application user follows least-privilege principles.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26705 — 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-26705 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