Skip to main content
VulnerabilityPublished Updated

CVE-2025-60736: SQL Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Dec 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 26 Oct 2026.

What to do

AI-suggested

Immediate mitigation should focus on restricting and sanitizing input to the vulnerable 'upass' parameter. Organizations should implement parameterized queries or prepared statements to prevent SQL Injection. Deploying a Web Application Firewall (WAF) with rules targeting SQL Injection patterns can provide a temporary protective layer. Monitoring database logs for unusual query patterns or failed login attempts can help detect exploitation attempts. Network segmentation should be used to limit access to the database server. Until an official patch or update is released by the software vendor, organizations should consider disabling or restricting access to the vulnerable login functionality if feasible. Conducting a thorough security audit of the application and related systems is recommended to identify other potential injection points. Finally, organizations should prepare incident response plans specific to data breaches involving medical information to comply with GDPR and other relevant regulations.

Description

code-projects Online Medicine Guide 1.0 is vulnerable to SQL Injection in /login.php via the upass parameter.

References

Community reviews

Loading reviews…