Skip to main content
CVE-2024-27515VulnerabilityPublished Updated

CVE-2024-27515: Osclass · n/a

Affects OsclassSource CVE Database V5

0

Not known to be exploited · CVSS 7.2 High.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Feb 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
GitHubmindstellar/Osclasspkg:github/mindstellar/OsclassOther threatsAffected
  • =5.1.2
Fixed in–

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

AI-suggested

1. Immediately restrict access to Osclass administrative interfaces to trusted IP addresses and use strong authentication mechanisms to prevent unauthorized access. 2. Monitor logs for unusual SQL errors or suspicious activity indicative of injection attempts. 3. Employ Web Application Firewalls (WAFs) with rules specifically targeting SQL Injection patterns to block malicious payloads. 4. Until an official patch is released, consider applying manual input validation and parameterized queries in the application code if feasible. 5. Regularly back up databases and verify backup integrity to enable recovery in case of data corruption or deletion. 6. Conduct security audits and penetration testing focused on injection flaws to identify and remediate similar vulnerabilities. 7. Stay informed about updates from Osclass developers and apply patches promptly once available. 8. Educate administrators and developers about the risks of SQL Injection and secure coding practices to prevent future occurrences.

Description

Osclass 5.1.2 is vulnerable to SQL Injection.

References

Community reviews

Loading reviews…