CVE-2025-6841: code-projects Product Inventory System · SQL Injection
Affects code-projects Product Inventory SystemSource CVE Database V5
Not known to be exploited · CVSS 5.1 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 29 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| code-projects Product Inventory System | Affected
| Fixed in– |
AI-suggested
European organizations should prioritize the following mitigations: 1) Restrict administrative access to the Product Inventory System through strong authentication mechanisms, including multi-factor authentication (MFA) and strict access controls to minimize the risk of privilege escalation. 2) Implement network segmentation and firewall rules to limit remote access to the administrative interface, ideally restricting it to trusted IP addresses or VPN connections. 3) Conduct thorough input validation and parameterized queries or prepared statements in the /admin/edit_product.php code to eliminate SQL injection vectors; if source code modification is not feasible immediately, consider deploying Web Application Firewalls (WAFs) with SQL injection detection rules as a temporary measure. 4) Monitor logs and audit trails for unusual administrative activities or SQL errors that could indicate exploitation attempts. 5) Engage with the vendor or community to obtain patches or updates addressing this vulnerability as soon as they become available. 6) Perform regular security assessments and penetration testing focusing on administrative interfaces to detect similar vulnerabilities proactively.
Description
A vulnerability has been found in code-projects Product Inventory System 1.0 and classified as critical. This vulnerability affects unknown code of the file /admin/edit_product.php. The manipulation of the argument ID leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.