# CVE-2017-20129: LogoStore search.php sql injection

> Remote attackers can exploit SQL injection in LogoStore's search.php to read sensitive database information.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-pfxq-pqj7-2jvr

## What is CVE-2017-20129?

CVE-2017-20129 is a medium-severity SQL injection vulnerability in unspecified LogoStore, published on 14 Jul 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in LogoStore. It has been classified as critical. Affected is an unknown function of the file /LogoStore/search.php. The manipulation of the argument query with the input test' UNION ALL SELECT CONCAT(CONCAT('qqkkq','VnPVWVaYxljWqGpLLbEIyPIHBjjjjASQTnaqfKaV'),'qvvpq'),NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL-- oCrh&search= leads to sql injection. It is possible to launch the attack remotely.

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

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

It affects 1 product.


Products: Logostore Project Logostore.

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

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

## Is CVE-2017-20129 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-20129 is a medium-severity SQL injection vulnerability in unspecified LogoStore, published on 14 Jul 2022. 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-20129 in the wild and no public exploit code.

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

## Sources

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

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