# CVE-2022-0513: WP Statistics <= 13.1.4 Unauthenticated Blind SQL Injection via exclusion_reason

> Unauthenticated attackers can inject SQL queries to read sensitive data if the Record Exclusions option is enabled.

- **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:** 16 Feb 2022
- **Updated:** 10 Feb 2025
- **Also known as:** GHSA-6gr9-x8m9-c46v

## What is CVE-2022-0513?

CVE-2022-0513 is a critical SQL injection vulnerability in VeronaLabs WP Statistics, published on 16 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP Statistics WordPress plugin is vulnerable to SQL Injection due to insufficient escaping and parameterization of the exclusion_reason parameter found in the ~/includes/class-wp-statistics-exclusion.php file which allows attackers without authentication to inject arbitrary SQL queries to obtain sensitive information, in versions up to and including 13.1.4. This requires the "Record Exclusions" option to be enabled on the vulnerable site.

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

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

It affects 1 product.


Products: Veronalabs Wp Statistics.

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

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

## Is CVE-2022-0513 being exploited?

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

## Other vulnerabilities in VeronaLabs WP Statistics

- [CVE-2022-38074](https://insights.sbomify.com/CVE-2022-38074/): WordPress WP Statistics Plugin <= 13.2.10 is vulnerable to SQL Injection (critical 9.9)
- [CVE-2022-0651](https://insights.sbomify.com/CVE-2022-0651/): WP Statistics <= 13.1.5 Unauthenticated Blind SQL Injection via current_page_type (critical 9.8)
- [CVE-2022-25148](https://insights.sbomify.com/CVE-2022-25148/): WP Statistics <= 13.1.5 Unauthenticated Blind SQL Injection via current_page_id (critical 9.8)
- [CVE-2022-25149](https://insights.sbomify.com/CVE-2022-25149/): WP Statistics <= 13.1.5 Unauthenticated Blind SQL Injection via IP (critical 9.8)
- [CVE-2017-18515](https://insights.sbomify.com/CVE-2017-18515/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-0513 is a critical SQL injection vulnerability in VeronaLabs WP Statistics, published on 16 Feb 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-0513 in the wild and no public exploit code.

Affected product: VeronaLabs WP Statistics. 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-0513/ (Markdown: https://insights.sbomify.com/CVE-2022-0513/index.md)
```

## Sources

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

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