# CVE-2022-3249: WP CSV Exporter < 1.3.7 - Admin+ SQLi

> Administrators can perform SQL injection attacks in the WP CSV Exporter plugin due to improper parameter sanitization.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Dec 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-7wqj-6cvm-fmfh

## What is CVE-2022-3249?

CVE-2022-3249 is a high-severity SQL injection vulnerability in Unknown WP CSV Exporter, published on 5 Dec 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The WP CSV Exporter WordPress plugin before 1.3.7 does not properly sanitise and escape some parameters before using them in a SQL statement, allowing high privilege users such as admin to perform SQL injection attacks

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

It affects 1 product.


Products: Wp Csv Exporter Project Wp Csv Exporter.

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

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

## Is CVE-2022-3249 being exploited?

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

## Other vulnerabilities in Unknown WP CSV Exporter

- [CVE-2022-3605](https://insights.sbomify.com/CVE-2022-3605/): WP CSV Exporter < 1.3.7 - CSV Injection (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3249 is a high-severity SQL injection vulnerability in Unknown WP CSV Exporter, published on 5 Dec 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3249 exists.

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

## Sources

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

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