# CVE-2017-16893: SQL injection in n/a

> Authenticated attackers can exploit SQL injection in tags.php to read database information via unsanitized edit_list parameters.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-vxp7-wxg7-j6qx

## What is CVE-2017-16893?

CVE-2017-16893 is a medium-severity SQL injection vulnerability in Piwigo Piwigo, published on 1 Dec 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The application Piwigo is affected by an SQL injection vulnerability in version 2.9.2 and possibly prior. This vulnerability allows remote authenticated attackers to obtain information in the context of the user used by the application to retrieve data from the database. tags.php is affected: values of the edit_list parameters are not sanitized; these are used to construct an SQL query and retrieve a list of registered users into the application.

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

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

It affects 1 product.


Products: Piwigo Piwigo.

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

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

## Is CVE-2017-16893 being exploited?

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

## Other vulnerabilities in Piwigo Piwigo

- [CVE-2014-4648](https://insights.sbomify.com/CVE-2014-4648/): Unspecified vulnerability in Piwigo before 2.6.3 has unknown impact and attack vectors, related to a "security failure." (critical 10.0)
- [CVE-2023-33361](https://insights.sbomify.com/CVE-2023-33361/): SQL injection in n/a (critical 9.8)
- [CVE-2023-33362](https://insights.sbomify.com/CVE-2023-33362/): SQL injection in n/a (critical 9.8)
- [CVE-2020-19213](https://insights.sbomify.com/CVE-2020-19213/): SQL injection in n/a (critical 9.8)
- [CVE-2021-32615](https://insights.sbomify.com/CVE-2021-32615/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-16893 is a medium-severity SQL injection vulnerability in Piwigo Piwigo, published on 1 Dec 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-16893 in the wild and no public exploit code.

Affected product: Piwigo Piwigo. 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-16893/ (Markdown: https://insights.sbomify.com/CVE-2017-16893/index.md)
```

## Sources

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

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