# CVE-2020-12507: s::can moni::tools autheticated SQL injection

> An authenticated attacker can exploit SQL injection in s::can moni::tools to gain full database access, compromising confidentiality, integrity, and availability.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Nov 2022
- **Updated:** 1 May 2025
- **Also known as:** GHSA-h6x8-4mx9-224h

## What is CVE-2020-12507?

CVE-2020-12507 is a high-severity SQL injection vulnerability in s::can moni:tools, published on 7 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In s::can moni::tools before version 4.2 an authenticated attacker could get full access to the database through SQL injection. This may result in loss of confidentiality, loss of integrity and DoS.

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

## Which versions are affected by CVE-2020-12507?

It affects 1 product.


Products: Badgermeter Moni\.

## How do I fix CVE-2020-12507?

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

## Is CVE-2020-12507 being exploited?

There is no known exploitation of CVE-2020-12507 in the wild and no public exploit code.

## Other vulnerabilities in s::can moni:tools

- [CVE-2020-12508](https://insights.sbomify.com/CVE-2020-12508/): s::can moni::tools prone to path traversal in image-relocator module (high 7.5)
- [CVE-2020-12509](https://insights.sbomify.com/CVE-2020-12509/): s::can moni::tools prone to path traversal in camera-file module (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-12507 and fix it if it is affected.

What it is: CVE-2020-12507 is a high-severity SQL injection vulnerability in s::can moni:tools, published on 7 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-12507 in the wild and no public exploit code.

Affected product: s::can moni:tools. 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-2020-12507/ (Markdown: https://insights.sbomify.com/CVE-2020-12507/index.md)
```

## Sources

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

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