Database read or modification via unsanitized fetch parameter
Published Jan 7, 2023 · Updated Aug 5, 2024
SQL injection in roxlukas LMeve 0.1.58 and earlier allows remote authenticated users to read or modify database data via the fetch parameter. The proxy.php handler reads fetch directly from the GET request before the insert_log audit path uses it, rather than applying the project's string-sanitization function. Exploitation requires a low-privileged session with adjacent-network access, and injected SQL executes with the application's database permissions.
Summary
What happened
SQL injection in roxlukas LMeve 0.1.58 and earlier allows remote authenticated users to read or modify database data via the fetch parameter. The proxy.php handler reads fetch directly from the GET request before the insert_log audit path uses it, rather than applying the project's string-sanitization function. Exploitation requires a low-privileged session with adjacent-network access, and injected SQL executes with the application's database permissions.
The record
- CVE
- CVE-2018-25071
- Published
- Jan 7, 2023
- Updated
- Aug 5, 2024
- Vendor
- roxlukas
- Product
- LMeve
- Classifications
- CWE-89, T1210
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 7, 2023CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=0.1.0
- Affected versionversion=0.1.1
- Affected versionversion=0.1.10
- Affected versionversion=0.1.11
- Affected versionversion=0.1.12
- Affected versionversion=0.1.13
- Affected versionversion=0.1.14
- Affected versionversion=0.1.15
- Affected versionversion=0.1.16
- Affected versionversion=0.1.17
- Affected versionversion=0.1.18
- Affected versionversion=0.1.19
- Affected versionversion=0.1.2
- Affected versionversion=0.1.20
- Affected versionversion=0.1.21
- Affected versionversion=0.1.22
- Affected versionversion=0.1.23
- Affected versionversion=0.1.24
- Affected versionversion=0.1.25
- Affected versionversion=0.1.26
- Affected versionversion=0.1.27
- Affected versionversion=0.1.28
- Affected versionversion=0.1.29
- Affected versionversion=0.1.3
- Affected versionversion=0.1.30
- Affected versionversion=0.1.31
- Affected versionversion=0.1.32
- Affected versionversion=0.1.33
- Affected versionversion=0.1.34
- Affected versionversion=0.1.35
- Affected versionversion=0.1.36
- Affected versionversion=0.1.37
- Affected versionversion=0.1.38
- Affected versionversion=0.1.39
- Affected versionversion=0.1.4
- Affected versionversion=0.1.40
- Affected versionversion=0.1.41
- Affected versionversion=0.1.42
- Affected versionversion=0.1.43
- Affected versionversion=0.1.44
- Affected versionversion=0.1.45
- Affected versionversion=0.1.46
- Affected versionversion=0.1.47
- Affected versionversion=0.1.48
- Affected versionversion=0.1.49
- Affected versionversion=0.1.5
- Affected versionversion=0.1.50
- Affected versionversion=0.1.51
- Affected versionversion=0.1.52
- Affected versionversion=0.1.53
- Affected versionversion=0.1.54
- Affected versionversion=0.1.55
- Affected versionversion=0.1.56
- Affected versionversion=0.1.57
- Affected versionversion=0.1.58
- Affected versionversion=0.1.6
- Affected versionversion=0.1.7
- Affected versionversion=0.1.8
- Affected versionversion=0.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