CVE-2025-46101
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSQL 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
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSQL injection vulnerability in Beakon LMS SCORM module via the unescaped 'ks' parameter in json_scorm.php allows remote attackers to inject arbitrary SQL queries, potentially exposing sensitive database contents including user credentials, course data, and other application records.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 5.4.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Beakon LMS installationLocate Beakon LMS installation directories on your web server. Check common web root locations or your documented installation path for a directory containing 'beakon' or 'lms' in the name.Affected if Beakon LMS is present on the server
-
Determine SCORM module versionLocate version information for the Beakon LMS SCORM module. Check for version files, manifest files (imsmanifest.xml), or admin interface version displays within the SCORM module directory. Compare the installed version number against the affected range of versions prior to 5.4.3.Affected if The installed SCORM module version is less than 5.4.3
-
Verify json_scorm.php existsSearch for the file 'json_scorm.php' within the Beakon LMS installation, particularly within SCORM-related directories. This file handles SCORM data operations and contains the vulnerable parameter handling.Affected if The json_scorm.php file exists in the installation
-
Confirm SCORM module is enabledCheck if the SCORM module is active and accessible on your Beakon LMS instance. Review the module configuration through the LMS admin interface or verify the SCORM functionality is accessible via web requests to SCORM-related endpoints.Affected if The SCORM module is enabled and accessible to users
Your environment is affected if you have Beakon LMS with a SCORM module version prior to 5.4.3 that has the json_scorm.php file accessible and the SCORM functionality enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped5.4.3
Upgrade to Beakon LMS SCORM version 5.4.3 or later which includes parameterized query implementation. If immediate patching is not possible, implement input validation and web application firewall rules for the json_scorm.php endpoint.
5.4.3 or later
- Identify the current version of Beakon Learning Management System SCORM installation
- Backup all database and application files before proceeding
- Download Beakon LMS SCORM version 5.4.3 or later from the official vendor
- Apply the upgrade following vendor documentation for your specific deployment method
- Verify the version has been updated to 5.4.3 or later
- Test that the json_scorm.php functionality works correctly after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46101 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-46101 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data