CVE-2025-8930: code-projects Medical Store Management System · SQL Injection
Affects code-projects Medical Store Management SystemSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 25 Oct 2026, 19:02 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:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 14 Aug 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 Medical Store Management System | Affected
| Fixed in– |
AI-suggested
European organizations should immediately audit their use of the code-projects Medical Store Management System version 1.0 and assess exposure to the UpdateCompany.java component. Specific mitigations include: 1) Implementing input validation and parameterized queries or prepared statements to prevent SQL injection in the 'companyNameTxt' parameter. 2) Applying web application firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting this parameter. 3) Restricting database user privileges to the minimum necessary to limit potential damage from injection attacks. 4) Monitoring logs for unusual query patterns or failed injection attempts. 5) Segregating the medical store management system network segment to limit lateral movement. 6) Engaging with the vendor or community to obtain patches or updates; if unavailable, consider migrating to alternative solutions with secure coding practices. 7) Conducting regular security assessments and penetration testing focusing on injection vulnerabilities. 8) Training staff on secure coding and input handling best practices if in-house development or customization is performed.
Description
A vulnerability was found in code-projects Medical Store Management System 1.0. This issue affects some unknown processing of the file UpdateCompany.java of the component Update Company Page. The manipulation of the argument companyNameTxt leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.