# CVE-2023-5082: History Log by click5 < 1.0.13 - Admin+ Time-Based Blind SQL Injection

> Admin users can exploit a SQL injection vulnerability in the History Log plugin when used with Smash Balloon Social Photo Feed to read database data.

- **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:** 6 Nov 2023
- **Updated:** 26 Feb 2025
- **Also known as:** GHSA-q2w4-425r-5cxw

## What is CVE-2023-5082?

CVE-2023-5082 is a high-severity SQL injection vulnerability in Unknown History Log by click5, published on 6 Nov 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The History Log by click5 WordPress plugin before 1.0.13 does not properly sanitise and escape a parameter before using it in a SQL statement, leading to a SQL injection exploitable by admin users when using the Smash Balloon Social Photo Feed plugin alongside it.

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

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

It affects 1 product.


Products: Click5interactive Sitemap by Click5.

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

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

## Is CVE-2023-5082 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-5082 is a high-severity SQL injection vulnerability in Unknown History Log by click5, published on 6 Nov 2023. 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-2023-5082 exists.

Affected product: Unknown History Log by click5. 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-5082/ (Markdown: https://insights.sbomify.com/CVE-2023-5082/index.md)
```

## Sources

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

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