# CVE-2019-13409: A SQL injection vulnerability was discovered in TOPMeeting before version 8.8 (2019/08/19)

> Attackers can exploit SQL injection in the search feature to extract database schema and credentials from TOPMeeting.

- **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:** 17 Oct 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-34jm-95xh-4rx8

## What is CVE-2019-13409?

CVE-2019-13409 is a critical SQL injection vulnerability in TOPOO Technology TOPMeeting, published on 17 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A SQL injection vulnerability was discovered in TOPMeeting before version 8.8 (2019/08/19). An attacker can use a union based injection query string though a search meeting room feature to get databases schema and username/password.

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

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

It affects 1 product.


Products: Topmeeting Topmeeting.

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

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

## Is CVE-2019-13409 being exploited?

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

## Other vulnerabilities in TOPOO Technology TOPMeeting

- [CVE-2019-13410](https://insights.sbomify.com/CVE-2019-13410/): TOPMeeting version before version 8.8 (2019/08/19) allows an attacker to obtain sensitive information (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-13409 is a critical SQL injection vulnerability in TOPOO Technology TOPMeeting, published on 17 Oct 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-13409 in the wild and no public exploit code.

Affected product: TOPOO Technology TOPMeeting. 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-13409/ (Markdown: https://insights.sbomify.com/CVE-2019-13409/index.md)
```

## Sources

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

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