# CVE-2023-5041: Track The Click < 0.3.12 - Author+ Time-Based Blind SQL Injection

> An authenticated author can perform time-based blind SQL injection via unsanitized REST API parameters to read database contents.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jan 2024
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-53gq-5qmj-xr28

## What is CVE-2023-5041?

CVE-2023-5041 is a high-severity SQL injection vulnerability in Unknown Track The Click, published on 17 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Track The Click WordPress plugin before 0.3.12 does not properly sanitize query parameters to the stats REST endpoint before using them in a database query, allowing a logged in user with an author role or higher to perform time based blind SQLi attacks on the database.

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

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

It affects 1 product.


Products: Tracktheclick Track the Click.

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

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

## Is CVE-2023-5041 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-5041 is a high-severity SQL injection vulnerability in Unknown Track The Click, published on 17 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-5041 exists.

Affected product: Unknown Track The Click. 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-5041/ (Markdown: https://insights.sbomify.com/CVE-2023-5041/index.md)
```

## Sources

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

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