CVE-2026-26704
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_category.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_category.php allows attackers to inject malicious SQL queries through unsanitized user input, potentially enabling unauthorized data access, data exfiltration, or full 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.
-
Locate the application directorySearch your web server document root for directories named 'pharmacy', 'pos', or 'pharmacy-point-of-sale'. Common paths include /var/www/html/, /htdocs/, or C:\inetpub\wwwroot\Affected if The pharmacy application directory exists on the server
-
Verify the application versionCheck for a version file, readme.txt, or any file containing '1.0' or 'Pharmacy Point of Sale' within the application directory. Alternatively, examine the footer or meta tags of any accessible page for version informationAffected if The installed version is exactly 1.0 (Oretnom23 Pharmacy Point Of Sale System)
-
Identify the vulnerable fileNavigate to the /pharmacy/ directory and confirm view_category.php exists. The full expected path is /pharmacy/view_category.php relative to your web rootAffected if The file view_category.php exists in the pharmacy directory
-
Inspect the SQL query implementationOpen view_category.php in a text editor and search for SQL queries (SELECT, INSERT, UPDATE, DELETE). Examine whether user-supplied input (from $_GET, $_POST, or $_REQUEST) is directly concatenated into SQL strings without using prepared statements, mysqli_prepare, or PDO parameter bindingAffected if The code contains unsanitized SQL queries that directly incorporate user input without parameterized queries
You are affected if the Pharmacy Point of Sale System v1.0 is installed and view_category.php contains SQL queries that concatenate user input directly into query strings.
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 dataReplace dynamic SQL queries with parameterized queries (prepared statements) in view_category.php to properly sanitize user input; apply principle of least privilege to the application database account.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26704 — 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-26704 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