# CVE-2025-46101: SQL injection in n/a

> Remote attackers can exploit SQL injection in Beakon LMS SCORM to obtain sensitive information via the ks parameter.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jun 2025
- **Updated:** 24 Jun 2025
- **Also known as:** GHSA-rj63-phmh-hrgw

## What is CVE-2025-46101?

CVE-2025-46101 is a critical SQL injection vulnerability in n/a, published on 23 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2025-46101?

It affects 1 product.


Products: Beakon Learning Management System Sharable Content Object Reference Model.

## How do I fix CVE-2025-46101?

No fix has been published for CVE-2025-46101 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-46101 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46101 exists.

## Other vulnerabilities in n/a

- [CVE-2025-46102](https://insights.sbomify.com/CVE-2025-46102/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-46101 and fix it if it is affected.

What it is: CVE-2025-46101 is a critical SQL injection vulnerability in n/a, published on 23 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46101 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-46101/ (Markdown: https://insights.sbomify.com/CVE-2025-46101/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-46101
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-46101
- OSV: https://osv.dev/vulnerability/CVE-2025-46101

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-46101/
Summaries are generated and may contain mistakes; the official description above is the record.