Security readout for executives and security teams
Plain-English summary
CVE-2017-20168 is a SQL injection issue in jfm-so piWallet. A low-privileged actor on an adjacent network could manipulate the api.php key argument and potentially affect limited confidentiality, integrity, and availability. The affected version range is not specified, so unpatched piWallet deployments should be treated as exposed until verified.
Executive priority
Prioritize remediation where piWallet is still in use on business or customer-facing wallet infrastructure. The known impact is moderate by CVSS, but SQL injection in wallet software deserves timely handling because exposure and version boundaries are incomplete.
Technical view
The source bundle identifies CWE-89 in piWallet api.php, where the key argument can be manipulated for SQL injection. CVSS 3.1 is 5.5 with AV:A, AC:L, PR:L, UI:N, and low C/I/A impact. The referenced fix is commit b420f8c4cbe7f06a34d1b05e90ee5cdfe0aa83bb.
Likely exposure
Exposure is limited to organizations running jfm-so piWallet with vulnerable api.php code reachable from adjacent network paths. Because affected versions are listed as n/a, inventory and code comparison are required rather than relying on version checks alone.
Exploitation context
The bundle does not report KEV listing or active exploitation. Sources describe the vulnerability and a patch, but do not provide complete affected-version data. The CVSS vector indicates exploitation requires adjacent network access and low privileges, with no user interaction.
Researcher notes
Do not assume a clean version boundary from the sources. Validate by patch presence and reachable attack surface. The description names api.php and the key argument, but says the affected functionality is otherwise unknown. No exploit confirmation is cited in the bundle.
Mitigation direction
- Apply the referenced piWallet patch commit b420f8c4cbe7f06a34d1b05e90ee5cdfe0aa83bb.
- Check the upstream pull request and vendor repository for current guidance.
- Restrict access to piWallet api.php to trusted networks where operationally feasible.
- Retire or isolate unsupported piWallet deployments if patching cannot be confirmed.
Validation and detection
- Inventory all piWallet deployments and confirm whether api.php is present.
- Compare deployed code against the referenced patch commit.
- Review access logs for unusual api.php requests involving the key argument.
- Confirm database permissions limit application account impact.
- Document any deployments where version or patch status cannot be proven.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2017-20168 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L2.13.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://vuldb.com/?id.218006CVE reference · vdb-entry, technical-description
- https://vuldb.com/?ctiid.218006CVE reference · signature, permissions-required
- https://github.com/jfm-so/piWallet/pull/23CVE reference · issue-tracking
- https://github.com/jfm-so/piWallet/commit/b420f8c4cbe7f06a34d1b05e90ee5cdfe0aa83bbCVE reference · patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.