Skip to main content
CVE-2025-14951VulnerabilityPublished Updated

CVE-2025-14951: code-projects Scholars Tracking System · SQL Injection

Affects code-projects Scholars Tracking SystemSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 18:53 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
GitHubgx922/CVEpkg:github/gx922/CVEOther threatsAffected
  • =1.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-14951, organizations should first verify if they are running version 1.0 of the code-projects Scholars Tracking System and prioritize upgrading to a patched version once available. In the absence of an official patch, immediate remediation includes implementing strict input validation and sanitization on the post_content parameter to prevent injection of malicious SQL code. Refactoring the code to use parameterized queries or prepared statements is essential to eliminate direct SQL concatenation vulnerabilities. Deploying a web application firewall (WAF) configured to detect and block SQL injection patterns can provide an additional protective layer. Regularly monitoring database logs and application behavior for unusual query patterns or anomalies can help detect exploitation attempts early. Organizations should also conduct security assessments and penetration testing focused on injection flaws to identify and remediate similar vulnerabilities. Finally, educating developers on secure coding practices and conducting code reviews can prevent recurrence of such issues.

Description

A security vulnerability has been detected in code-projects Scholars Tracking System 1.0. The impacted element is an unknown function of the file /home.php. Such manipulation of the argument post_content leads to sql injection. The attack can be executed remotely. The exploit has been disclosed publicly and may be used.

References

Community reviews

Loading reviews…