# CVE-2022-0817: BadgeOS <= 3.7.0 - Unauthenticated SQLi

> Unauthenticated attackers can execute arbitrary SQL commands via an AJAX action in the BadgeOS WordPress plugin, potentially accessing or modifying database content.

- **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:** 9 May 2022
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-xx94-r2jp-2426

## What is CVE-2022-0817?

CVE-2022-0817 is a critical SQL injection vulnerability in Unknown BadgeOS, published on 9 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The BadgeOS WordPress plugin through 3.7.0 does not sanitise and escape a parameter before using it in a SQL statement via an AJAX action, leading to an SQL Injection exploitable by unauthenticated users

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

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

It affects 1 product.


Products: Badgeos Badgeos.

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

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

## Is CVE-2022-0817 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-0817 exists.

Public exploit code:

- WordPress BadgeOS <=3.7.0 - SQL Injection (nuclei): http/cves/2022/CVE-2022-0817.yaml

## Other vulnerabilities in Unknown BadgeOS

- [CVE-2023-2173](https://insights.sbomify.com/CVE-2023-2173/): BadgeOS <= 3.7.1.6 - Authenticated (Subscriber+) Insecure Direct Object Reference to Arbitrary Post Deletion (medium 6.5)
- [CVE-2022-41987](https://insights.sbomify.com/CVE-2022-41987/): WordPress BadgeOS Plugin <= 3.7.1.6 is vulnerable to Cross Site Request Forgery (CSRF) (medium 6.3)
- [CVE-2023-2171](https://insights.sbomify.com/CVE-2023-2171/): BadgeOS <= 3.7.1.6 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode (medium 5.4)
- [CVE-2023-2172](https://insights.sbomify.com/CVE-2023-2172/): BadgeOS <= 3.7.1.6 - Authenticated (Subscriber+) Insecure Direct Object Reference to Arbitrary Post Title Overwrite (medium 4.3)
- [CVE-2023-2174](https://insights.sbomify.com/CVE-2023-2174/): BadgeOS <= 3.7.1.6 - Missing Authorization in delete_badgeos_log_entries (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-0817 is a critical SQL injection vulnerability in Unknown BadgeOS, published on 9 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-0817 exists.

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

## Sources

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

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