# CVE-2022-3131: Search Logger <= 0.9 - Admin+ SQLi

> A SQL injection vulnerability in the Search Logger WordPress plugin allows high-privilege users to manipulate database queries.

- **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:** 17 Oct 2022
- **Updated:** 14 May 2025
- **Also known as:** GHSA-p363-w8j5-w3rq

## What is CVE-2022-3131?

CVE-2022-3131 is a high-severity SQL injection vulnerability in Unknown Search Logger – Know What Your Visitors Search, published on 17 Oct 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Search Logger WordPress plugin through 0.9 does not properly sanitise and escape a parameter before using it in a SQL statement, leading to a SQL injection exploitable by high privilege users

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

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

It affects 1 product.


Products: Codexpert Search Logger.

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

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

## Is CVE-2022-3131 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3131 is a high-severity SQL injection vulnerability in Unknown Search Logger – Know What Your Visitors Search, published on 17 Oct 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-3131 exists.

Affected product: Unknown Search Logger – Know What Your Visitors Search. 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-3131/ (Markdown: https://insights.sbomify.com/CVE-2022-3131/index.md)
```

## Sources

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

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