CVE-2026-10255
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 · uneditedA vulnerability has been found in SourceCodester Pharmacy Sales and Inventory System 1.0. Affected by this vulnerability is the function sell_statement of the file application/controllers/ShowForm.php. Such manipulation leads to improper access controls. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.
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 Sales and Inventory System 1.0 contains an improper access control vulnerability in the sell_statement function within application/controllers/ShowForm.php. The function lacks proper authorization checks, allowing remote attackers to access sensitive sales reporting functionality without authentication. This could expose confidential pharmacy sales data and transaction records.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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 if Pharmacy Sales and Inventory System is installedLocate the application installation directory and check for the presence of application/controllers/ShowForm.php fileAffected if The application directory contains ShowForm.php in the controllers folder
-
Verify the vulnerable function existsOpen application/controllers/ShowForm.php and search for the sell_statement function definitionAffected if The file contains a function named sell_statement without authorization logic
-
Check for missing authorization in sell_statementInspect the sell_statement function code to see if it includes session validation, role checks, or permission verification before returning dataAffected if The function directly returns sales statement data without verifying user authentication or authorization
-
Test unauthenticated access to the endpointSend a request to the sell_statement function endpoint (typically index.php/ShowForm/sell_statement or similar) without providing valid session credentialsAffected if The application returns sales data without requiring authentication or returns an error indicating missing authorization checks
-
Verify sales data scope restrictionCheck if the function filters data based on the authenticated user's permissions or scope (e.g., user_id, branch_id)Affected if The function returns all sales records regardless of which user is requesting the data
A user is affected if they run Pharmacy Sales and Inventory System 1.0 with the ShowForm.php controller containing an unprotected sell_statement function that returns sales data without verifying user authorization.
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 proper authentication and role-based access control (RBAC) in the ShowForm.php controller's sell_statement function. Ensure all sensitive functions verify user session validity and appropriate role permissions before executing.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10255 — 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-10255 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