# CVE-2023-6030: LogDash Activity Log < 1.1.4 - Unauthenticated SQLi

> Unauthenticated attackers can exploit SQL injection in the LogDash Activity Log plugin to read database information via time-based techniques.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **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:** 15 May 2025
- **Updated:** 16 May 2025
- **Also known as:** GHSA-2v7w-p95j-mfhp

## What is CVE-2023-6030?

CVE-2023-6030 is a medium-severity SQL injection vulnerability in Unknown LogDash Activity Log, published on 15 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The LogDash Activity Log WordPress plugin before 1.1.4 hooks the wp_login_failed function (from src/Hooks/Users.php) in order to log failed login attempts to the database but it doesn't escape the username when it perform some SQL request leading to a SQL injection vulnerability which can be exploited using time-based technique by unauthenticated attacker

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

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

It affects 1 product.


Products: Deryckoe Logdash Activity Log.

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

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

## Is CVE-2023-6030 being exploited?

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

Public exploit code:

- LogDash Activity Log <= 1.1.3 - SQL Injection (nuclei): http/cves/2023/CVE-2023-6030.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2023-6030 is a medium-severity SQL injection vulnerability in Unknown LogDash Activity Log, published on 15 May 2025. 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-6030 exists.

Affected product: Unknown LogDash Activity Log. 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-6030/ (Markdown: https://insights.sbomify.com/CVE-2023-6030/index.md)
```

## Sources

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

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