CVE-2025-6834: code-projects Inventory Management System · SQL Injection
Affects code-projects Inventory Management SystemSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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:PExploitation evidence
Disclosed: evidence found.
CVE published 28 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-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| code-projects Inventory Management System | Affected
| Fixed in– |
AI-suggested
Organizations should immediately audit their use of the code-projects Inventory Management System and identify any instances of version 1.0 in their environment. Input validation and parameterized queries should be enforced at the application level if source code access is possible. Network segmentation should be applied to isolate the inventory management system from critical internal resources. Monitoring and logging of database queries and web application logs should be enhanced to detect suspicious activity. Organizations should also consider temporary disabling or restricting access to the vulnerable endpoint until a patch is released. Finally, they should maintain close communication with the vendor for timely patch deployment once available.
Description
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/editPayment.php. The manipulation of the argument orderId leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.