# CVE-2018-12942: SQL injection in n/a

> Authenticated attackers can inject SQL commands in SeedDMS to extract, modify, or delete database information and potentially execute system commands.

- **Severity:** High 8.8 (`CVSS:3.0/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:** 31 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-p7gq-5m2c-hfh3

## What is CVE-2018-12942?

CVE-2018-12942 is a high-severity SQL injection vulnerability in n/a, published on 31 Jul 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SQL injection vulnerability in the "Users management" functionality in SeedDMS (formerly LetoDMS and MyDMS) before 5.1.8 allows authenticated attackers to manipulate an SQL query within the application by sending additional SQL commands to the application server. An attacker can use this vulnerability to perform malicious tasks such as to extract, change, or delete sensitive information within the database supporting the application, and potentially run system commands on the underlying operating system.

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

## Which versions are affected by CVE-2018-12942?

It affects 1 product.


Products: Seeddms Seeddms.

## How do I fix CVE-2018-12942?

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

## Is CVE-2018-12942 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-44938](https://insights.sbomify.com/CVE-2022-44938/): Weak cryptography in n/a (critical 9.8)
- [CVE-2021-33223](https://insights.sbomify.com/CVE-2021-33223/): Privilege escalation in n/a (high 8.8)
- [CVE-2018-12940](https://insights.sbomify.com/CVE-2018-12940/): File upload in n/a (high 8.8)
- [CVE-2018-12941](https://insights.sbomify.com/CVE-2018-12941/): Command injection in n/a (high 8.8)
- [CVE-2019-12744](https://insights.sbomify.com/CVE-2019-12744/): File upload in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-12942 and fix it if it is affected.

What it is: CVE-2018-12942 is a high-severity SQL injection vulnerability in n/a, published on 31 Jul 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-12942 in the wild and no public exploit code.

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-2018-12942/ (Markdown: https://insights.sbomify.com/CVE-2018-12942/index.md)
```

## Sources

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

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