Authenticated SQL injection via blog search parameter
Published Jul 16, 2023 · Updated Aug 2, 2024
SQL injection in QuickQR 6.3.7 allows remote authenticated users to alter database queries through the s parameter on /blog. The undisclosed GET parameter handler incorporates attacker-controlled s input into an SQL command without neutralizing special elements. A valid low-privilege account is required, and successful exploitation can read or modify limited database data and interrupt service.
Summary
What happened
SQL injection in QuickQR 6.3.7 allows remote authenticated users to alter database queries through the s parameter on /blog. The undisclosed GET parameter handler incorporates attacker-controlled s input into an SQL command without neutralizing special elements. A valid low-privilege account is required, and successful exploitation can read or modify limited database data and interrupt service.
The record
- CVE
- CVE-2023-3689
- Published
- Jul 16, 2023
- Updated
- Aug 2, 2024
- Vendor
- Bylancer
- Product
- QuickQR
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 16, 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=6.3.7
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