Skip to main content
CVE-2024-37870VulnerabilityPublished Updated

CVE-2024-37870: cve1 · n/a

Affects cve1Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Jul 2024

  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
GitHubtthuyyy/cve1pkg:github/tthuyyy/cve1Other 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-2024-37870, organizations should immediately review and update the processscore.php script to implement parameterized queries or prepared statements, eliminating direct concatenation of user input into SQL commands. Input validation should be enforced to ensure the id parameter accepts only expected data types and values. Web application firewalls (WAFs) can be configured to detect and block SQL injection patterns targeting the id parameter. Monitoring database logs for unusual queries or access patterns can help identify exploitation attempts early. If patching the LMS source code is not immediately feasible, consider restricting external access to the vulnerable script via network controls or authentication mechanisms. Educate developers on secure coding practices to prevent similar vulnerabilities. Regular security assessments and code reviews should be conducted to detect injection flaws proactively. Finally, maintain backups of critical data to enable recovery in case of data corruption or loss.

Description

SQL injection vulnerability in processscore.php in Learning Management System Project In PHP With Source Code 1.0 allows attackers to execute arbitrary SQL commands via the id parameter.

References

Community reviews

Loading reviews…