CVE-2025-14950

7.3

code-projects · Scholars Tracking System

A SQL injection vulnerability exists in the Scholars Tracking System 1.0 delete_post.php file, allowing unauthenticated attackers to manipulate database queries via the id parameter.

Executive summary

An unauthenticated SQL injection vulnerability in the code-projects Scholars Tracking System 1.0 poses a significant risk of unauthorized database access and potential system compromise.

Vulnerability

This vulnerability is a SQL injection flaw (CWE-89) located in the /sts/delete_post.php file. It stems from improper sanitization of the id parameter, which allows an unauthenticated attacker to execute arbitrary SQL commands.

Business impact

Successful exploitation of this vulnerability can lead to unauthorized access to sensitive information, data tampering, or complete database compromise. Given the CVSS score of 7.3, this flaw is categorized as High severity, as it allows remote attackers to bypass application security controls to interact directly with the backend database.

Remediation

Immediate Action: Since no official patch is currently available, administrators should restrict access to the /sts/delete_post.php endpoint via network controls or disable the affected functionality until a vendor update is released.

Proactive Monitoring: Monitor web server access logs for anomalous GET requests containing SQL syntax, such as UNION, SELECT, or SLEEP commands, directed at the delete_post.php file.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block common SQL injection patterns targeting the id parameter.

Exploitation status

Public Exploit Available: Yes, a proof-of-concept exists and is documented in the researcher's GitHub issue report (https://github.com/gx922/CVE/issues/2).

Analyst recommendation

Due to the availability of a public proof-of-concept and the lack of an official patch, this vulnerability presents a credible risk to any environment hosting the Scholars Tracking System. Organizations should prioritize isolating the affected application from public-facing networks and implement strict input validation or WAF filtering to mitigate the risk of exploitation until official remediation is provided by the vendor.

More code-projects CVEs

Sources

Originally found and disclosed by guanyingxin (VulDB User), per the CVE Program record.