CVE-2025-8953: SourceCodester COVID 19 Testing Management System · SQL Injection
Affects SourceCodester COVID 19 Testing 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.4% chance of exploitation in 30 days – higher than 37% 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 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 |
|---|---|---|
| SourceCodester COVID 19 Testing Management System | Affected
| Fixed in– |
AI-suggested
Organizations should immediately audit their use of SourceCodester COVID 19 Testing Management System version 1.0 and isolate any exposed instances. Specific mitigations include: 1) Implementing Web Application Firewalls (WAFs) with SQL injection detection and prevention rules tailored to the /check_availability.php endpoint and the employeeid parameter. 2) Applying input validation and parameterized queries or prepared statements in the application code to prevent SQL injection, if source code access is available. 3) Restricting network access to the application to trusted internal networks or VPNs to reduce exposure. 4) Monitoring logs for suspicious queries or unusual access patterns targeting the vulnerable parameter. 5) Segregating the database with least privilege principles to limit the impact of a successful injection. 6) Planning for an upgrade or patch deployment once the vendor releases a fix. 7) Conducting regular security assessments and penetration tests focusing on injection flaws. These steps go beyond generic advice by focusing on immediate containment, detection, and architectural controls specific to this vulnerability and product.
Description
A vulnerability was determined in SourceCodester COVID 19 Testing Management System 1.0. Affected by this issue is some unknown functionality of the file /check_availability.php. The manipulation of the argument employeeid leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.