CVE-2025-13583

7.3 HIGH

📋 TL;DR

This vulnerability allows remote attackers to execute SQL injection attacks against Question Paper Generator 1.0 by manipulating the Fname parameter in the /signupscript.php file. Attackers can potentially access, modify, or delete database content. All users running the vulnerable version of this software are affected.

💻 Affected Systems

Products:
  • Question Paper Generator
Versions: 1.0
Operating Systems: All platforms running PHP
Default Config Vulnerable: ⚠️ Yes
Notes: Affects the /signupscript.php component when handling POST parameters.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data theft, data destruction, and potential remote code execution on the database server.

🟠

Likely Case

Unauthorized data access, data manipulation, and potential privilege escalation within the application.

🟢

If Mitigated

Limited impact with proper input validation and database permissions in place.

🌐 Internet-Facing: HIGH - The vulnerability is remotely exploitable and a public exploit exists.
🏢 Internal Only: MEDIUM - Still exploitable by internal attackers but requires network access.

🎯 Exploit Status

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

Exploit details are publicly available and the vulnerability is in a common attack vector (SQL injection).

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

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

Restart Required: No

Instructions:

No official patch available. Consider implementing input validation and parameterized queries as workarounds.

🔧 Temporary Workarounds

Input Validation for Fname Parameter

all

Add server-side validation to sanitize and validate the Fname parameter before processing.

Edit /signupscript.php to add input validation: $fname = mysqli_real_escape_string($connection, $_POST['Fname']);

Web Application Firewall Rule

all

Implement WAF rules to block SQL injection patterns in POST requests to /signupscript.php.

Add WAF rule: Block requests to /signupscript.php containing SQL keywords in POST parameters

🧯 If You Can't Patch

  • Isolate the vulnerable system from internet access and restrict internal network access.
  • Implement strict database permissions and monitor for unusual database queries.

🔍 How to Verify

Check if Vulnerable:

Test the /signupscript.php endpoint with SQL injection payloads in the Fname parameter.

Check Version:

Check the software version in the application interface or configuration files.

Verify Fix Applied:

Verify that SQL injection attempts no longer succeed and that input validation is properly implemented.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in database logs
  • Multiple failed login attempts or parameter manipulation in web server logs

Network Indicators:

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

SIEM Query:

source="web_server" AND url="/signupscript.php" AND (param="Fname" AND value CONTAINS "UNION" OR value CONTAINS "SELECT" OR value CONTAINS "--")

🔗 References

📤 Share & Export