CVE-2025-7475

7.3 HIGH

📋 TL;DR

A critical SQL injection vulnerability in Simple Car Rental System 1.0 allows remote attackers to execute arbitrary SQL commands via the 'mpesa' parameter in /pay.php. This affects all deployments of version 1.0 that have the vulnerable file accessible. Attackers can potentially read, modify, or delete database content.

💻 Affected Systems

Products:
  • Simple Car Rental System
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Any installation with /pay.php accessible is vulnerable. No special configuration required.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data theft, data destruction, or full system takeover via SQL injection to RCE chaining.

🟠

Likely Case

Unauthorized database access allowing extraction of sensitive information like customer data, payment details, and credentials.

🟢

If Mitigated

Limited impact with proper input validation and WAF rules blocking SQL injection patterns.

🌐 Internet-Facing: HIGH - The vulnerability is remotely exploitable and affects a web-facing component.
🏢 Internal Only: MEDIUM - Internal attackers could exploit this if they have network access to the system.

🎯 Exploit Status

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

Exploit details are publicly available on GitHub, making this easy to weaponize.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://code-projects.org/

Restart Required: No

Instructions:

No official patch available. Consider upgrading to a newer version if available, or implement workarounds.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Add proper input validation and parameterized queries to /pay.php to sanitize the 'mpesa' parameter.

Edit /pay.php to use prepared statements with parameterized queries for all database operations

Web Application Firewall Rules

all

Deploy WAF rules to block SQL injection patterns targeting the /pay.php endpoint.

Add WAF rule: deny requests to /pay.php containing SQL keywords in parameters

🧯 If You Can't Patch

  • Restrict network access to the system using firewall rules to allow only trusted IPs.
  • Disable or remove /pay.php if not required for business operations.

🔍 How to Verify

Check if Vulnerable:

Test /pay.php with SQL injection payloads in the 'mpesa' parameter and observe database errors or unexpected behavior.

Check Version:

Check the software version in the admin panel or configuration files.

Verify Fix Applied:

After implementing fixes, retest with SQL injection payloads to confirm they are blocked or sanitized.

📡 Detection & Monitoring

Log Indicators:

  • SQL syntax errors in web server logs
  • Unusual database queries from web application
  • Multiple failed login attempts via /pay.php

Network Indicators:

  • HTTP requests to /pay.php with SQL keywords in parameters
  • Unusual outbound database connections from web server

SIEM Query:

source="web_logs" AND uri="/pay.php" AND (param="mpesa" AND value MATCHES "(?i)(union|select|insert|delete|update|drop|--|#|;)")

🔗 References

📤 Share & Export