CVE-2026-14695: SQL Injection in SourceCodester Grocery Management System 1.0
A SQL injection vulnerability exists in SourceCodester Multi-Vendor Online Grocery Management System version 1.0, specifically in the user registration function. An attacker can send a malicious request with a specially crafted name field to bypass input validation and execute arbitrary SQL commands against the backend database. No authentication is required, and the vulnerability can be exploited over the network. Public proof-of-concept code has been released, making this an active threat.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 7.3 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
- Weaknesses (CWE)
- CWE-74, CWE-89
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-07-05 / 2026-07-07
NVD description (verbatim)
A vulnerability was found in SourceCodester Multi-Vendor Online Grocery Management System 1.0. This affects the function save_client of the file classes/Users.php of the component Registration Handler. The manipulation of the argument Name results in sql injection. It is possible to launch the attack remotely. The exploit has been made public and could be used.
6 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-14695 is a SQL injection flaw in the save_client function within classes/Users.php of the Registration Handler component. The Name parameter is not properly sanitized before being incorporated into a SQL query, allowing an unauthenticated attacker to inject arbitrary SQL syntax. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L) reflects network-based attack surface, low complexity, and impact across confidentiality, integrity, and availability. The vulnerability maps to CWE-74 (Improper Neutralization of Special Elements in Output) and CWE-89 (SQL Injection).
Business impact
Organizations deploying SourceCodester Multi-Vendor Online Grocery Management System 1.0 face direct risk of data breach, data manipulation, and potential service disruption. An attacker exploiting this flaw could extract customer information, order history, and payment records; modify transaction records; or delete critical data. If the system handles inventory management or supply chain operations, attackers could disrupt stock levels and fulfillment operations. The public availability of exploit code accelerates the likelihood of opportunistic attacks.
Affected systems
SourceCodester Multi-Vendor Online Grocery Management System version 1.0 is confirmed affected. The vulnerability resides in the user registration workflow, meaning any installation accepting new user signups is vulnerable. Verify whether your organization runs this specific version; the vendor/product metadata should be checked against the vendor's official documentation for scope confirmation.
Exploitability
This vulnerability is readily exploitable with low technical barriers. Network accessibility requires no authentication, no user interaction, and minimal attack complexity. The public disclosure of exploit code removes the exploitation research burden. An attacker can craft a simple HTTP request with SQL metacharacters (e.g., single quotes, UNION statements) in the Name field to retrieve, modify, or delete database records. Active exploitation is likely given the public PoC availability and the high-value target (e-commerce system with customer data).
Remediation
Immediate action is required. Apply security patches provided by SourceCodester as soon as available; check the vendor's security advisory for fixed version numbers and deployment instructions. As a temporary control, restrict access to the registration endpoint via Web Application Firewall (WAF) rules that block common SQL injection patterns or require additional verification. Conduct a database audit to identify any unauthorized data access or modifications since the system was deployed.
Patch guidance
Contact SourceCodester directly or review their security advisories to obtain patched version information; verify patch version numbers against official vendor channels before deployment. Apply patches to all affected instances in development, staging, and production environments. Test patches thoroughly in a non-production environment to ensure compatibility with customizations or integrations. After patching, conduct a code review of the Registration Handler and related input-handling functions to identify similar injection vectors.
Detection guidance
Monitor application logs and database query logs for unusual SQL syntax patterns in the Name parameter, such as single quotes, UNION statements, comments (--), or xp_/sp_ stored procedure calls. Implement Web Application Firewall (WAF) rules to detect and block SQL injection attempts. Query database audit logs for unexpected SELECT, INSERT, UPDATE, or DELETE operations from the registration context. Search for HTTP requests to the registration endpoint containing encoded or obfuscated SQL keywords (e.g., %27, %55NION). Correlate registration attempts with subsequent anomalous database activity.
Why prioritize this
This vulnerability warrants immediate patching due to the combination of high CVSS score (7.3), unauthenticated network exploitation, public exploit availability, and direct access to sensitive customer data. The attack requires no user interaction or special privileges, making it attractive to both opportunistic and targeted adversaries. The business criticality of an e-commerce system—handling customer records and transactions—amplifies the risk. Organizations running version 1.0 should treat this as a critical remediation priority.
Risk score, explained
The CVSS 3.1 score of 7.3 (HIGH) reflects a network-accessible flaw with low attack complexity and no authentication barrier. The vector indicates impact to confidentiality (data theft), integrity (data manipulation), and availability (service disruption). While the scope is unchanged (the attacker cannot elevate privilege beyond the database user context), the combination of trivial exploitability and high-value target justifies the HIGH severity. The public PoC elevates practical risk beyond the base score.
Frequently asked questions
How do I know if my organization uses SourceCodester Multi-Vendor Online Grocery Management System?
Check your application inventory for SourceCodester products. Look for 'SourceCodester' in vendor documentation, licensing files, or code repositories. If you operate an online grocery platform or e-commerce site, check application metadata and version information in admin panels or configuration files. Consult your procurement and IT asset management systems for records of SourceCodester software purchases.
Can this vulnerability be exploited without network access?
No. The CVSS vector AV:N indicates the vulnerability is exploitable over the network from an unauthenticated attacker position. There is no requirement for local system access, code execution privileges, or user interaction. Any entity capable of making HTTP requests to the registration endpoint can attempt exploitation.
What should I do if I cannot patch immediately?
Implement compensating controls: deploy WAF rules blocking SQL injection patterns in the Name parameter; restrict registration endpoint access by IP allowlist if feasible; enforce strict input validation on the client side as a temporary measure (though not a substitute for server-side patching); monitor database and application logs intensively for exploitation attempts; consider temporarily disabling new user registration if the business allows. These are temporary measures only—pursue patching as the priority.
Is this vulnerability currently being actively exploited in the wild?
The vulnerability is not officially tracked in CISA's Known Exploited Vulnerabilities (KEV) catalog, but public exploit code has been released. This significantly increases the likelihood of opportunistic exploitation. Assume active attacks are occurring or will occur imminently, and prioritize patching accordingly.
This analysis is provided for informational and educational purposes based on available vulnerability data as of the publication date. SEC.co does not manufacture, endorse, or distribute SourceCodester products and makes no warranty regarding vendor patch availability or compatibility. Organizations must verify patch version numbers and compatibility against official vendor security advisories before deployment. Active exploitation cannot be guaranteed or ruled out; threat landscape assessment should incorporate additional threat intelligence sources and organizational risk context. This document does not constitute professional security advice tailored to your specific environment; consult qualified security professionals for deployment decisions. Source: NVD (public-domain), retrieved 2026-08-13. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2026-10110HIGHSQL Injection in code-projects Student Details Management System 1.0
- CVE-2026-10111HIGHSQL Injection in sambitraj STUDENT-MANAGEMENT-SYSTEM 1.0 Login
- CVE-2026-10178HIGHSQL Injection in code-projects Online Music Site 1.0 Admin Panel
- CVE-2026-10184HIGHSQL Injection in SourceCodester Hospitals Patient Records System 1.0
- CVE-2026-10185HIGHSQL Injection in SourceCodester Hospitals Patient Records Management System 1.0
- CVE-2026-10186HIGHSQL Injection in Online Hospital Management System 1.0 – Remote Code Execution Risk
- CVE-2026-10208HIGHSQL Injection in Online Hospital Management System Login
- CVE-2026-10225HIGHSQL Injection in PHP Student Management System Login