# CVE-2015-10066: tynx wuersch Store.class.php getByCustomQuery sql injection

> SQL injection in tynx wuersch allows attackers to manipulate database queries via the getByCustomQuery function, requiring a patch.

- **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:** 17 Jan 2023
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-66rw-9q89-rr6x

## What is CVE-2015-10066?

CVE-2015-10066 is a medium-severity SQL injection vulnerability in tynx wuersch, published on 17 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 tynx wuersch and classified as critical. Affected by this issue is the function packValue/getByCustomQuery of the file backend/base/Store.class.php. The manipulation leads to sql injection. The patch is identified as 66d4718750a741d1053d327a79e285fd50372519. It is recommended to apply a patch to fix this issue. VDB-218462 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-2015-10066?

It affects 1 product.


Products: Wuersch Project Wuersch.

## How do I fix CVE-2015-10066?

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

## Is CVE-2015-10066 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-10066 and fix it if it is affected.

What it is: CVE-2015-10066 is a medium-severity SQL injection vulnerability in tynx wuersch, published on 17 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-2015-10066 in the wild and no public exploit code.

Affected product: tynx wuersch. 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-2015-10066/ (Markdown: https://insights.sbomify.com/CVE-2015-10066/index.md)
```

## Sources

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

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