EUVD-2025-19110Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Input neutralization, injection prevention
|
| Impact | The CVSS 3.1 score of 7.3 with vector AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L indicates HIGH risk: network-accessible (AV:N), low attack complexity (AC:L), no privileges required (PR:N), and no user interaction needed (UI:N). The impact scope is unchanged (S:U) but all three impact categories (confidentiality, integrity, availability) are affected at low level. The public disclosure and confirmed POC availability elevate practical risk significantly. This is NOT a case of high-CVSS-but-low-real-risk; SQL injection on an unauthenticated endpoint with public exploit code represents a GENUINE and IMMEDIATE threat requiring urgent patching. Organizations running this software should prioritize remediation due to demonstrated exploitability and low attack barrier. |
| Exploit ScenarioDerived | An attacker crafts a malicious HTTP request to the vulnerable createBrand.php endpoint with a payload in the brandStatus parameter such as: |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 15, 2026
CVE-2025-6611 is a critical SQL injection vulnerability in code-projects Inventory Management System 1.0 affecting the /php_action/createBrand.php endpoint via the brandStatus parameter. The vulnerability allows unauthenticated remote attackers to manipulate SQL queries, potentially resulting in unauthorized data access, modification, or deletion. Public exploit disclosure and active exploitation risk are confirmed.
RemediationAI
- IMMEDIATE: Disable or restrict access to /php_action/createBrand.php via web application firewall (WAF) rules until patch is available.
- Apply input validation: Implement strict whitelisting for brandStatus parameter (e.g., only allow alphanumeric characters or specific enum values).
- Use prepared statements/parameterized queries: Replace all direct SQL string concatenation with parameterized queries using bound variables in PHP (MySQLi prepared statements or PDO prepared statements).
- Implement output encoding: Ensure all user input is properly escaped using context-appropriate escaping functions (e.g., mysqli_real_escape_string or prepared statements).
- Monitor vendor advisories: Check code-projects official repository/website for security patches to Inventory Management System v1.0. If no patch is available, consider migrating to a maintained alternative or hardening via WAF rules.
- Apply principle of least privilege: Ensure database user executing createBrand.php queries has minimal required permissions (no DROP/ALTER TABLE rights).
- Conduct security testing: Perform SQL injection testing on all similar endpoints (other /php_action/*.php files with user-controlled parameters) to identify related vulnerabilities.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability exists in PHP-based web application code (specifically createBrand.php) that fails to properly sanitize or parameterize user input in the brandStatus parameter before constructing SQL queries. This is a classic CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component - 'Injection') vulnerability. The root cause is likely missing input validation, lack of prepared statements, or inadequate escaping of SQL special characters. The affected product is code-projects Inventory Management System v1.0, a PHP-based inventory management application. The attack surface is exposed through a publicly accessible web endpoint with no authentication requirement (PR:N in CVSS).
Know when Inventory Management System gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
4DescriptionCVE.org
A vulnerability was found in code-projects Inventory Management System 1.0. It has been declared as critical. This vulnerability affects unknown code of the file /php_action/createBrand.php. The manipulation of the argument brandStatus leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.
Executive ViewAI
A critical SQL injection vulnerability in the Inventory Management System 1.0 allows unauthenticated remote attackers to manipulate database queries through the brand status parameter, potentially exposing or modifying sensitive inventory and business data. With public exploit code available and no patch currently released, this poses an immediate risk to any organization using this system.
Implement WAF rules to filter SQL injection payloads in the /php_action/createBrand.php endpoint; restrict network access to the application via IP allowlisting or VPN; disable the brand creation feature if not critical to operations; apply strict input validation and parameterized queries at the application level if source code access is available; monitor database logs for suspicious queries; segment the database server from general network access.
Threat Intelligence Overview
NVD
CVE.org
EPSS
GitHub
VulDB
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
More in Inventory Management System
View allA vulnerability, which was classified as critical, was found in SourceCodester Inventory Management System 1.0. Rated cr
A vulnerability classified as critical was found in SourceCodester Inventory Management System 1.0. Rated critical sever
A vulnerability, which was classified as critical, has been found in SourceCodester Inventory Management System 1.0.php.
A vulnerability was found in SourceCodester Inventory Management System 1.0 and classified as critical.php. Rated critic
A vulnerability has been found in SourceCodester Inventory Management System 1.0 and classified as critical. Rated criti
Sourcecodester Free and Open Source inventory management system v1.0 is vulnerable to Incorrect Access Control. Rated hi
A vulnerability was found in SourceCodester Free and Open Source Inventory Management System 1.0. Rated high severity (C
A vulnerability, which was classified as critical, was found in SourceCodester Inventory Management System 1.0. Rated hi
A vulnerability classified as critical has been found in SourceCodester Inventory Management System 1.0. Rated critical
A vulnerability has been found in SourceCodester Inventory Management System 1.0 and classified as critical. Rated criti
A vulnerability, which was classified as critical, was found in SourceCodester Inventory Management System 1.0. Rated cr
A vulnerability was found in SourceCodester Inventory Management System 1.0 and classified as critical.php. Rated critic
Exploit-DB