Database disclosure via unescaped failed-login username
Published May 15, 2025 · Updated May 16, 2025
SQL injection in Deryckoe LogDash Activity Log before 1.1.4 allows remote attackers to read WordPress database data via failed logins. The wp_login_failed hook in src/Hooks/Users.php inserts the supplied username into a database query without escaping or sufficient preparation. No authentication or user interaction is required, and a time-based blind query can extract password hashes and other accessible database values.
Summary
What happened
SQL injection in Deryckoe LogDash Activity Log before 1.1.4 allows remote attackers to read WordPress database data via failed logins. The wp_login_failed hook in src/Hooks/Users.php inserts the supplied username into a database query without escaping or sufficient preparation. No authentication or user interaction is required, and a time-based blind query can extract password hashes and other accessible database values.
The record
- CVE
- CVE-2023-6030
- Published
- May 15, 2025
- Updated
- May 16, 2025
- Vendor
- Deryckoe
- Product
- LogDash Activity Log
- Classifications
- CWE-89, T1190, T1555
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 15, 2025CVE publishedPublication date reported by the CVE source.
- May 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.1.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- WPScan time-based blind SQL injection proof of conceptfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo