# CVE-2022-0814: Ubigeo de Peru < 3.6.4 - Unauthenticated SQLi

> Unauthenticated attackers can exploit SQL injection vulnerabilities in the Ubigeo de Perú 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-87xq-353v-p7cw

## What is CVE-2022-0814?

CVE-2022-0814 is a critical SQL injection vulnerability in Unknown Ubigeo de Perú para Woocommerce y WordPress, 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 Ubigeo de Perú para Woocommerce WordPress plugin before 3.6.4 does not properly sanitise and escape some parameters before using them in SQL statements via various AJAX actions, some of which are available to unauthenticated users, leading to SQL Injections

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

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

It affects 1 product.


Products: Ubigeo De Peru Para Woocommerce Project Ubigeo De Peru Para Woocommerce.

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

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

## Is CVE-2022-0814 being exploited?

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

Public exploit code:

- Ubigeo de Peru < 3.6.4 - SQL Injection (nuclei): http/cves/2022/CVE-2022-0814.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2022-0814 is a critical SQL injection vulnerability in Unknown Ubigeo de Perú para Woocommerce y WordPress, 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-0814 exists.

Affected product: Unknown Ubigeo de Perú para Woocommerce y WordPress. 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-0814/ (Markdown: https://insights.sbomify.com/CVE-2022-0814/index.md)
```

## Sources

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

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