CVE-2025-60736

9.8 CRITICAL

📋 TL;DR

Online Medicine Guide 1.0 contains a SQL injection vulnerability in the login.php page's upass parameter. This allows attackers to execute arbitrary SQL commands on the database. All users running this specific version are affected.

💻 Affected Systems

Products:
  • code-projects Online Medicine Guide
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Only version 1.0 is confirmed vulnerable. The vulnerability exists in the default installation.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data theft, authentication bypass, remote code execution, or database destruction.

🟠

Likely Case

Authentication bypass allowing unauthorized access to the application, followed by data exfiltration or manipulation.

🟢

If Mitigated

Limited impact if proper input validation and parameterized queries are implemented.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Public proof-of-concept exists on GitHub. Exploitation requires no authentication and uses simple SQL injection techniques.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: Unknown

Restart Required: No

Instructions:

No official patch available. Consider implementing parameterized queries or input validation as workaround.

🔧 Temporary Workarounds

Implement Input Validation

all

Add server-side validation to reject SQL injection patterns in the upass parameter.

Use Parameterized Queries

all

Modify login.php to use prepared statements instead of concatenating user input into SQL queries.

🧯 If You Can't Patch

  • Implement a web application firewall (WAF) with SQL injection rules
  • Restrict access to login.php to trusted IP addresses only

🔍 How to Verify

Check if Vulnerable:

Test login.php with SQL injection payloads in the upass parameter (e.g., ' OR '1'='1).

Check Version:

Check application version in admin panel or configuration files.

Verify Fix Applied:

Attempt SQL injection after implementing fixes; successful login should only occur with valid credentials.

📡 Detection & Monitoring

Log Indicators:

  • Multiple failed login attempts with SQL patterns in parameters
  • Unusual database query errors in application logs

Network Indicators:

  • HTTP POST requests to login.php containing SQL keywords in parameters

SIEM Query:

source="web_logs" AND uri="/login.php" AND (request_body CONTAINS "OR" OR request_body CONTAINS "UNION" OR request_body CONTAINS "SELECT")

🔗 References

📤 Share & Export