CVE-2025-13290

6.3 MEDIUM

📋 TL;DR

This SQL injection vulnerability in Simple Food Ordering System 1.0 allows attackers to manipulate database queries through the /saveorder.php endpoint. Attackers can potentially read, modify, or delete database contents remotely. All deployments of version 1.0 with the vulnerable file accessible are affected.

💻 Affected Systems

Products:
  • Simple Food Ordering System
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Any installation with /saveorder.php accessible is vulnerable. The vulnerability is in the core application code.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data theft, data manipulation, or deletion of the entire food ordering system database

🟠

Likely Case

Extraction of sensitive customer data (names, addresses, payment info), order manipulation, or system disruption

🟢

If Mitigated

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

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploit details are publicly available on GitHub. SQL injection is a well-understood attack vector with many automated tools available.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

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

Restart Required: No

Instructions:

1. Check vendor website for updates 2. If no patch available, implement workarounds 3. Consider replacing with alternative software

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Add parameterized queries and input validation to /saveorder.php

Modify saveorder.php to use prepared statements: $stmt = $conn->prepare('INSERT INTO orders (id, ...) VALUES (?, ...)'); $stmt->bind_param('i', $id);

Web Application Firewall Rules

all

Block SQL injection patterns targeting /saveorder.php

Add WAF rule: SecRule REQUEST_URI "@contains /saveorder.php" "id:1001,phase:2,deny,msg:'SQLi attempt on saveorder.php'"

🧯 If You Can't Patch

  • Block external access to /saveorder.php using firewall rules or web server configuration
  • Implement network segmentation to isolate the food ordering system from sensitive databases

🔍 How to Verify

Check if Vulnerable:

Test /saveorder.php endpoint with SQL injection payloads like ' OR '1'='1 in the ID parameter

Check Version:

Check application files or documentation for version information

Verify Fix Applied:

Attempt SQL injection tests and verify they are blocked or properly handled without database errors

📡 Detection & Monitoring

Log Indicators:

  • Unusual database queries from web server
  • SQL syntax errors in application logs
  • Multiple failed requests to /saveorder.php

Network Indicators:

  • SQL keywords (SELECT, UNION, etc.) in POST requests to /saveorder.php
  • Unusual database connection patterns

SIEM Query:

source="web_logs" AND uri="/saveorder.php" AND (message="*sql*" OR message="*database*" OR message="*syntax*")

🔗 References

📤 Share & Export