Skip to main content
CVE-2025-6819VulnerabilityPublished Updated

CVE-2025-6819: code-projects Inventory Management System · SQL Injection

Affects code-projects Inventory Management SystemSource CVE Database V5

0

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.5% chance of exploitation in 30 days – higher than 42% 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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
code-projects Inventory Management SystemAffected
  • =1.0
Fixed in–

AI-suggested

Immediate mitigation steps include implementing strict input validation and parameterized queries or prepared statements to prevent SQL injection in the 'brandId' parameter. Organizations should audit their usage of the code-projects Inventory Management System version 1.0 and isolate or restrict access to the vulnerable endpoint (/php_action/removeBrand.php) via network controls such as firewalls or web application firewalls (WAFs) configured to detect and block SQL injection patterns. Monitoring and logging database queries and web requests targeting this endpoint can help detect exploitation attempts. Until an official patch is released, consider applying virtual patching through WAF rules or disabling the affected functionality if feasible. Regular backups of the database should be maintained to enable recovery in case of data tampering. Additionally, organizations should review user privileges on the database to minimize the potential damage from injection attacks. Finally, updating to a patched or newer version of the software once available is critical.

Description

A vulnerability has been found in code-projects Inventory Management System 1.0 and classified as critical. Affected by this vulnerability is an unknown functionality of the file /php_action/removeBrand.php. The manipulation of the argument brandId leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…