CVE-2026-37149
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 · uneditedGROCERY-STORE-MANAGEMENT-SYSTEM-USING-PHP-AND-MYSQL-PHPMYADMIN v1.0 was discovered to contain a SQL injection vulnerability in the scost parameter in /grocery/search_products.php. This vulnerability allows attackers to access sensitive database information via a crafted SQL statement.
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 · high confidenceThis is a SQL injection vulnerability in the grocery-store-management-system v1.0. The scost parameter in /grocery/search_products.php is not properly sanitized, allowing attackers to inject malicious SQL statements through this input to exfiltrate sensitive database information.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.
-
Locate the grocery-store-management-system installationSearch the web server document root for a directory named 'grocery' containing search_products.php, or look for files matching 'search_products.php' across the systemAffected if The application directory 'grocery' with search_products.php exists on the server
-
Confirm the application version is v1.0Check for version indicators such as a VERSION file, composer.json, or any readme/setup documentation within the grocery application directoryAffected if The installed version is grocery-store-management-system v1.0
-
Inspect the search_products.php file for the scost parameter handlingOpen /grocery/search_products.php and locate the code that processes the 'scost' GET or POST parameter; examine how it is incorporated into SQL queriesAffected if The scost parameter is directly concatenated into SQL queries without prepared statements, parameter binding, or sanitization
-
Verify the application is connected to a databaseCheck the application configuration files (such as config.php, db.php, or similar) to confirm database connection credentials and that a database is in useAffected if The application uses a database and the vulnerable code is accessible to process requests
-
Test for the vulnerability (if authorized and in test environment)Send a crafted request to search_products.php with a scost parameter value like '1' OR '1'='1' to observe if unsanitized SQL is executedAffected if The application returns unexpected database results or errors indicating SQL injection is possible
You are affected if grocery-store-management-system v1.0 is installed and the search_products.php file contains direct SQL concatenation of the scost parameter without prepared statements.
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 dataFix by implementing prepared statements/parameterized queries for the scost parameter in search_products.php, and apply input validation. Also apply least-privilege principle to the database user.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-37149 — 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-37149 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