SQL injection via unvalidated admin.php lid parameter
Published Sep 17, 2023 · Updated Aug 2, 2024
SQL injection in LmxCMS 1.0 through 1.41 allows attackers to execute unintended database queries through the admin.php lid argument. The published record identifies lid as the tainted argument but does not disclose the affected query, input transformation, or missing validation operation. VulDB requires low-privileged adjacent-network access, while NVD rates the flaw as remotely unauthenticated; public evidence does not resolve the discrepancy.
Summary
What happened
SQL injection in LmxCMS 1.0 through 1.41 allows attackers to execute unintended database queries through the admin.php lid argument. The published record identifies lid as the tainted argument but does not disclose the affected query, input transformation, or missing validation operation. VulDB requires low-privileged adjacent-network access, while NVD rates the flaw as remotely unauthenticated; public evidence does not resolve the discrepancy.
The record
- CVE
- CVE-2023-5017
- Published
- Sep 17, 2023
- Updated
- Aug 2, 2024
- Vendor
- LmxCMS
- Product
- LmxCMS
- Classifications
- CWE-89, T1190
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 17, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record 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=1.0
- Affected versionversion=1.1
- Affected versionversion=1.10
- Affected versionversion=1.11
- Affected versionversion=1.12
- Affected versionversion=1.13
- Affected versionversion=1.14
- Affected versionversion=1.15
- Affected versionversion=1.16
- Affected versionversion=1.17
- Affected versionversion=1.18
- Affected versionversion=1.19
- Affected versionversion=1.2
- Affected versionversion=1.20
- Affected versionversion=1.21
- Affected versionversion=1.22
- Affected versionversion=1.23
- Affected versionversion=1.24
- Affected versionversion=1.25
- Affected versionversion=1.26
- Affected versionversion=1.27
- Affected versionversion=1.28
- Affected versionversion=1.29
- Affected versionversion=1.3
- Affected versionversion=1.30
- Affected versionversion=1.31
- Affected versionversion=1.32
- Affected versionversion=1.33
- Affected versionversion=1.34
- Affected versionversion=1.35
- Affected versionversion=1.36
- Affected versionversion=1.37
- Affected versionversion=1.38
- Affected versionversion=1.39
- Affected versionversion=1.4
- Affected versionversion=1.40
- Affected versionversion=1.41
- Affected versionversion=1.5
- Affected versionversion=1.6
- Affected versionversion=1.7
- Affected versionversion=1.8
- Affected versionversion=1.9
What conditions does exploitation require?
What is affected?
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
No public exploit references are available in this record.
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