# CVE-2019-12720: SQL injection in n/a

> An attacker can exploit SQL injection vulnerabilities in AUO SunVeillance Monitoring System to read privileged data from the server.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Nov 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-fpcm-j34w-8cjw

## What is CVE-2019-12720?

CVE-2019-12720 is a high-severity SQL injection vulnerability in n/a, published on 12 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

AUO SunVeillance Monitoring System before v1.1.9e is vulnerable to mvc_send_mail.aspx (MailAdd parameter) SQL Injection. An Attacker can carry a SQL Injection payload to the server, allowing the attacker to read privileged data. This also affects the picture_manage_mvc.aspx plant_no parameter, the swapdl_mvc.aspx plant_no parameter, and the account_management.aspx Text_Postal_Code and Text_Dis_Code parameters.

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

## Which versions are affected by CVE-2019-12720?

It affects 1 product.


Products: Auo Sunveillance Monitoring System \& Data Recorder.

## How do I fix CVE-2019-12720?

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

## Is CVE-2019-12720 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-12719](https://insights.sbomify.com/CVE-2019-12719/): File upload in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-12720 and fix it if it is affected.

What it is: CVE-2019-12720 is a high-severity SQL injection vulnerability in n/a, published on 12 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-12720 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-2019-12720/ (Markdown: https://insights.sbomify.com/CVE-2019-12720/index.md)
```

## Sources

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

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