# CVE-2022-39303: Ree6 vulnerable to SQL Injection

> Attackers can manipulate SQL queries in the Ree6 moderation bot, potentially reading or modifying data, requiring an upgrade to the patched version.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/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:** 13 Oct 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-69xv-xjfw-4pv8

## What is CVE-2022-39303?

CVE-2022-39303 is a high-severity SQL injection vulnerability in Ree6-Applications Ree6, published on 13 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Ree6 is a moderation bot. This vulnerability allows manipulation of SQL queries. This issue has been patched in version 1.7.0 by using Javas PreparedStatements, which allow object setting without the risk of SQL injection. There are currently no known workarounds.

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

## Which versions are affected by CVE-2022-39303?

It affects 1 product.


Products: Ree6 Ree6.

## How do I fix CVE-2022-39303?

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

## Is CVE-2022-39303 being exploited?

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

## Other vulnerabilities in Ree6-Applications Ree6

- [CVE-2022-39302](https://insights.sbomify.com/CVE-2022-39302/): Ree6 may bypass webhook protection (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-39303 and fix it if it is affected.

What it is: CVE-2022-39303 is a high-severity SQL injection vulnerability in Ree6-Applications Ree6, published on 13 Oct 2022. 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-2022-39303 in the wild and no public exploit code.

Affected product: Ree6-Applications Ree6. 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-2022-39303/ (Markdown: https://insights.sbomify.com/CVE-2022-39303/index.md)
```

## Sources

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

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