# CVE-2026-18666: Library Management System < 3.6.7 - Subscriber+ SQL Injection via Filter Value

> Subscribers can perform SQL injection to extract arbitrary database data, including password hashes, in the Library Management System plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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:** 10 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-2c9h-p9wv-wmqh

## What is CVE-2026-18666?

CVE-2026-18666 is a medium-severity SQL injection vulnerability in Unknown Library Management System, published on 10 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Library Management System WordPress plugin before 3.6.7 does not sanitize and escape a user-supplied parameter before using it in a SQL statement, allowing users with a role as low as Subscriber to perform SQL injection and extract arbitrary data from the database, including user password hashes.

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

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


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

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

## Is CVE-2026-18666 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18666 is a medium-severity SQL injection vulnerability in Unknown Library Management System, published on 10 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-18666 in the wild and no public exploit code.

Affected product: Unknown Library Management System. 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-18666/ (Markdown: https://insights.sbomify.com/CVE-2026-18666/index.md)
```

## Sources

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

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