# CVE-2017-20168: jfm-so piWallet api.php sql injection

> An attacker can perform SQL injection via the key argument in api.php, potentially reading or modifying database contents.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jan 2023
- **Updated:** 9 Apr 2025
- **Also known as:** GHSA-qfcc-2wxx-3qm9

## What is CVE-2017-20168?

CVE-2017-20168 is a medium-severity SQL injection vulnerability in jfm-so piWallet, published on 11 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in jfm-so piWallet. It has been rated as critical. Affected by this issue is some unknown functionality of the file api.php. The manipulation of the argument key leads to sql injection. The patch is identified as b420f8c4cbe7f06a34d1b05e90ee5cdfe0aa83bb. It is recommended to apply a patch to fix this issue. VDB-218006 is the identifier assigned to this vulnerability.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2017-20168?

It affects 1 product.


Products: Piwallet Project Piwallet.

## How do I fix CVE-2017-20168?

No fix has been published for CVE-2017-20168 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-20168 being exploited?

There is no known exploitation of CVE-2017-20168 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-20168 and fix it if it is affected.

What it is: CVE-2017-20168 is a medium-severity SQL injection vulnerability in jfm-so piWallet, published on 11 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-20168 in the wild and no public exploit code.

Affected product: jfm-so piWallet. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-20168/ (Markdown: https://insights.sbomify.com/CVE-2017-20168/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-20168
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-20168
- OSV: https://osv.dev/vulnerability/CVE-2017-20168

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-20168/
Summaries are generated and may contain mistakes; the official description above is the record.