# CVE-2026-110179: affiliate-toolkit < 3.8.9 - Editor+ SQL Injection via orderby Parameter

> Editor-level users can perform SQL injection via the orderby parameter to read arbitrary database information, including super admin password hashes on multisite.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-x236-2cg8-2gw8

## What is CVE-2026-110179?

CVE-2026-110179 is a medium-severity SQL injection vulnerability in Unknown affiliate-toolkit, published on 16 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The affiliate-toolkit  WordPress plugin before 3.8.9 does not validate a user-supplied sort value against an allowlist before using it in a database query, and the affected administrative list screen requires only a lower-privilege capability rather than an administrator one, so users with editor-level access and above can perform SQL injection and read arbitrary information from the database. On multisite a sub-site editor can read the network-global users table, including the super administrator's password hash.

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

## Which versions are affected by CVE-2026-110179?


## How do I fix CVE-2026-110179?

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

## Is CVE-2026-110179 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-110179 and fix it if it is affected.

What it is: CVE-2026-110179 is a medium-severity SQL injection vulnerability in Unknown affiliate-toolkit, published on 16 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-110179 in the wild and no public exploit code.

Affected product: Unknown affiliate-toolkit. 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-2026-110179/ (Markdown: https://insights.sbomify.com/CVE-2026-110179/index.md)
```

## Sources

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

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