CVE-2025-6501VulnerabilityPublished 23 Jun 2025

CVE-2025-6501: 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

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 41% 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:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 23 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubmex135605/cve`pkg:github/mex135605/cve`Other threats	Affected =1.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate mitigation should focus on restricting external access to the Inventory Management System, ideally isolating it behind firewalls or VPNs to limit exposure to untrusted networks. 2. Implement Web Application Firewall (WAF) rules specifically designed to detect and block SQL Injection attempts targeting the 'categoriesStatus' parameter. 3. Conduct thorough input validation and sanitization on all user-supplied data, particularly the 'categoriesStatus' parameter, using parameterized queries or prepared statements to prevent SQL Injection. 4. If source code access is available, apply patches or code fixes to properly handle input validation; if not, consider disabling or restricting the vulnerable functionality until a patch is released. 5. Monitor logs for unusual database query patterns or errors indicative of injection attempts. 6. Regularly back up inventory data and verify backup integrity to enable recovery in case of data tampering or loss. 7. Engage with the vendor or community to obtain updates or patches as soon as they become available. 8. Educate IT staff and users about the risks and signs of exploitation to improve detection and response capabilities.

Description

A vulnerability, which was classified as critical, was found in code-projects Inventory Management System 1.0. This affects an unknown part of the file /php_action/createCategories.php. The manipulation of the argument categoriesStatus leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations using the code-projects Inventory Management System 1.0, this vulnerability poses a significant risk to the confidentiality, integrity, and availability of inventory data. Successful exploitation could lead to unauthorized access to sensitive business information, manipulation or deletion of inventory records, and disruption of business operations. This is particularly impactful for sectors relying heavily on accurate inventory management such as retail, manufacturing, and logistics. Given the remote exploitability without authentication, attackers could leverage this vulnerability to establish persistent access or pivot to other internal systems, potentially leading to broader network compromise. The medium CVSS score suggests that while the vulnerability is serious, the overall impact might be limited by the scope of the affected system and the presence of other security controls. However, organizations lacking proper network segmentation or monitoring could face elevated risks. Additionally, the public availability of exploit code increases the likelihood of opportunistic attacks, especially targeting less mature security environments common in smaller enterprises.

Summary

CVE-2025-6501 is a critical SQL Injection vulnerability identified in version 1.0 of the code-projects Inventory Management System, specifically within the /php_action/createCategories.php file. The vulnerability arises from improper sanitization or validation of the 'categoriesStatus' parameter, which an attacker can manipulate to inject malicious SQL code. This injection flaw allows remote attackers to execute arbitrary SQL commands on the backend database without requiring authentication or user interaction. The vulnerability is remotely exploitable over the network, increasing its risk profile. Although the exact database backend is unspecified, typical SQL Injection impacts include unauthorized data disclosure, data modification, or deletion, and potentially full system compromise if leveraged to escalate privileges or execute system commands via the database. The CVSS 4.0 score is 6.9, categorized as medium severity, reflecting the ease of exploitation (no privileges or user interaction needed) but limited scope of impact (low confidentiality, integrity, and availability impact). No known exploits are currently reported in the wild, but public disclosure of the exploit code increases the likelihood of exploitation attempts. The vulnerability affects only version 1.0 of the Inventory Management System, which is a niche product primarily used for managing inventory data, likely in small to medium enterprises. The lack of available patches or mitigations at the time of publication increases the urgency for affected users to implement workarounds or protective controls.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Jun 2025, 03:34 UTC

Technical details

References

Community reviews

Related threats