# CVE-2024-54820: SQL injection in n/a

> Attackers can extract all usernames and passwords from XOne Web Monitor via SQL injection on the login page.

- **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:** 24 Feb 2025
- **Updated:** 24 Feb 2025
- **Also known as:** GHSA-jv22-92xx-9w46

## What is CVE-2024-54820?

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

### Official description

XOne Web Monitor v02.10.2024.530 framework 1.0.4.9 was discovered to contain a SQL injection vulnerability in the login page. This vulnerability allows attackers to extract all usernames and passwords via a crafted input.

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

## Which versions are affected by CVE-2024-54820?


## How do I fix CVE-2024-54820?

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

## Is CVE-2024-54820 being exploited?

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

Public exploit code:

- Vuln disclosure for XOne app (github_poc): https://github.com/jcarabantes/CVE-2024-54820

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-54820 and fix it if it is affected.

What it is: CVE-2024-54820 is a critical SQL injection vulnerability in n/a, published on 24 Feb 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-2024-54820 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-2024-54820/ (Markdown: https://insights.sbomify.com/CVE-2024-54820/index.md)
```

## Sources

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

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