Database access via unescaped API key
Published Jan 11, 2023 · Updated Apr 9, 2025
SQL injection in piWallet api.php allows remote authenticated users to execute SQL through a crafted key parameter. api.php assigns the key GET parameter without escaping it before using the value in a MySQL statement. The CNA assessment requires low privileges and adjacent-network access; successful injection can read or alter wallet database records.
Summary
What happened
SQL injection in piWallet api.php allows remote authenticated users to execute SQL through a crafted key parameter. api.php assigns the key GET parameter without escaping it before using the value in a MySQL statement. The CNA assessment requires low privileges and adjacent-network access; successful injection can read or alter wallet database records.
The record
- CVE
- CVE-2017-20168
- Published
- Jan 11, 2023
- Updated
- Apr 9, 2025
- Vendor
- jfm-so
- Product
- piWallet
- Classifications
- CWE-89, T1190
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 11, 2023CVE publishedPublication date reported by the CVE source.
- Apr 9, 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=n/a
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