# CVE-2023-34168: WordPress WP Report Post Plugin <= 2.1.2 is vulnerable to SQL Injection

> Attackers can execute arbitrary SQL commands via the WP Report Post plugin, potentially reading or modifying database contents.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Dec 2023
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-9g4p-qmx2-m5mj

## What is CVE-2023-34168?

CVE-2023-34168 is a high-severity SQL injection vulnerability in Alex Raven WP Report Post, published on 18 Dec 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Alex Raven WP Report Post allows SQL Injection.This issue affects WP Report Post: from n/a through 2.1.2.

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

## Which versions are affected by CVE-2023-34168?

It affects 1 product.


Products: Esiteq Wp Report Post.

## How do I fix CVE-2023-34168?

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

## Is CVE-2023-34168 being exploited?

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

## Other vulnerabilities in Alex Raven WP Report Post

- [CVE-2023-34171](https://insights.sbomify.com/CVE-2023-34171/): WordPress WP Report Post Plugin <= 2.1.2 is vulnerable to Cross Site Request Forgery (CSRF) (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-34168 and fix it if it is affected.

What it is: CVE-2023-34168 is a high-severity SQL injection vulnerability in Alex Raven WP Report Post, published on 18 Dec 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-34168 in the wild and no public exploit code.

Affected product: Alex Raven WP Report Post. 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-2023-34168/ (Markdown: https://insights.sbomify.com/CVE-2023-34168/index.md)
```

## Sources

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

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