CVE-2025-6889

7.3 HIGH

📋 TL;DR

This critical SQL injection vulnerability in code-projects Movie Ticketing System 1.0 allows remote attackers to execute arbitrary SQL commands via the postName parameter in /logIn.php. Attackers can potentially access, modify, or delete database content. All systems running this software with the vulnerable component exposed are affected.

💻 Affected Systems

Products:
  • code-projects Movie Ticketing System
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Any installation with /logIn.php accessible is vulnerable. The vulnerability is in the core authentication component.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data theft, data destruction, authentication bypass, and potential remote code execution via database functions.

🟠

Likely Case

Unauthorized database access leading to sensitive data exposure (user credentials, payment info, personal data) and potential system takeover.

🟢

If Mitigated

Limited impact with proper input validation and database permissions, potentially only error messages or partial data exposure.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Public exploit available on GitHub. SQL injection via postName parameter requires no authentication.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

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

Restart Required: No

Instructions:

No official patch available. Consider migrating to alternative software or implementing custom fixes with parameterized queries.

🔧 Temporary Workarounds

Input Validation Filter

all

Add input validation to sanitize postName parameter before SQL processing

Modify /logIn.php to include: $postName = mysqli_real_escape_string($connection, $_POST['postName']);

Web Application Firewall

all

Deploy WAF with SQL injection rules to block malicious requests

🧯 If You Can't Patch

  • Isolate the system behind a reverse proxy with strict input filtering
  • Implement network segmentation to limit database access from web server

🔍 How to Verify

Check if Vulnerable:

Test /logIn.php endpoint with SQL injection payloads in postName parameter (e.g., ' OR '1'='1)

Check Version:

Check software documentation or configuration files for version information

Verify Fix Applied:

Verify parameterized queries are implemented and test with SQL injection payloads returns proper error handling

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL error messages in application logs
  • Multiple failed login attempts with SQL-like patterns in postName

Network Indicators:

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

SIEM Query:

source="web_logs" AND uri="/logIn.php" AND (postName CONTAINS "OR" OR postName CONTAINS "UNION" OR postName CONTAINS "SELECT")

🔗 References

📤 Share & Export