# CVE-2022-0836: SEMA API < 4.02 - Unauthenticated SQLi

> Unauthenticated attackers can exploit SQL injection in the SEMA API WordPress plugin to read or modify database contents.

- **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-63q4-pj3x-xhww

## What is CVE-2022-0836?

CVE-2022-0836 is a critical SQL injection vulnerability in Unknown SEMA API, 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 SEMA API WordPress plugin before 4.02 does not properly sanitise and escape some parameters before using them in SQL statements via an AJAX action, leading to SQL Injections exploitable by unauthenticated users

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

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

It affects 1 product.


Products: Semadatacoop Sema Api.

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

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

## Is CVE-2022-0836 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-0836 is a critical SQL injection vulnerability in Unknown SEMA API, published on 9 May 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-0836 in the wild and no public exploit code.

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

## Sources

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

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