Skip to main content
CVE-2025-46101VulnerabilityPublished Updated

CVE-2025-46101: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · fixed in 5.4.3 : patch affected systems as a priority.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.4.3
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 23 Jun 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 26 Oct 2026.

What to do

AI-suggested

To mitigate this vulnerability, European organizations should prioritize upgrading Beakon LMS to version 5.4.3 or later as soon as the patch becomes available. In the interim, organizations should implement web application firewalls (WAFs) with custom rules to detect and block suspicious SQL injection patterns targeting the 'ks' parameter in json_scorm.php. Conduct thorough input validation and sanitization on all user-supplied parameters, especially those interacting with the database. Employ least privilege principles for database accounts used by the LMS to limit the scope of data exposure in case of compromise. Regularly audit LMS logs for unusual access patterns or failed SQL queries indicative of attempted exploitation. Additionally, segment the LMS infrastructure within the network to restrict lateral movement if an attacker gains access. Educate LMS administrators and users about the risks and signs of exploitation attempts. Finally, maintain up-to-date backups of LMS data to enable recovery in case of data integrity issues or ransomware attacks following exploitation.

Description

SQL Injection vulnerability in Beakon Software Beakon Learning Management System Sharable Content Object Reference Model (SCORM) version before 5.4.3 allows a remote attacker to obtain sensitive information via the ks parameter in json_scorm.php file

References

Community reviews

Loading reviews…