CVE-2023-6030: The LogDash Activity Log WordPress plugin before 1.1.4 hooks the wp_login_failed function (from src/Hooks/User

Q: How do I fix CVE-2023-6030?

logdash activity log: upgrade to 1.1.4. Exact commands for each OS are on this page.

Q: Is CVE-2023-6030 being exploited?

CVE-2023-6030 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2023-6030 affect?

CVE-2023-6030 affects logdash activity log. Severity is medium (CVSS 5.4). 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 l

Q: How urgent is CVE-2023-6030?

Priority 38/100. Public exploit reference

Routine

MEDIUM 5.4UPGRADE

CVE-2023-6030 is a medium-severity flaw (CVSS 5.4) affecting logdash activity log. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	5.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.9% (top 42%)
CISA exploited list	No
Weakness	CWE-89
Published	2025-05-15
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: deryckoe

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-05-15 20:15 UTCPublished CVE record published
2026-06-17 06:49 UTCUpdated Record last modified

deryckoe logdash activity log UPGRADE

Affected: < 1.1.4

Fixed in: 1.1.4

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy logdash-activity-log || rpm -q logdash-activity-log || logdash-activity-log --version

2. UPGRADE to 1.1.4 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade logdash-activity-log

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade logdash-activity-log

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Nuclei scan template: LogDash Activity Log <= 1.1.3 - SQL Injection

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2023-6030?

logdash activity log: upgrade to 1.1.4. Exact commands for each OS are on this page.

Is CVE-2023-6030 being exploited?

CVE-2023-6030 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2023-6030 affect?

CVE-2023-6030 affects logdash activity log. Severity is medium (CVSS 5.4). 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 l

How urgent is CVE-2023-6030?

Priority 38/100. Public exploit reference

Software pages

WordPress vulnerabilities · PHP vulnerabilities

References

← Back to latest CVEs