# CVE-2026-14231: LifterLMS < 10.0.10 - Subscriber+ Sensitive Information Disclosure via select2_query_posts

> Authenticated subscribers can read internal post titles like coupon codes due to missing capability checks in an AJAX handler.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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:** 30 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** GHSA-hqvc-w7p2-cpm5

## What is CVE-2026-14231?

CVE-2026-14231 is a medium-severity missing authorization vulnerability in Unknown LifterLMS, published on 30 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The LifterLMS  WordPress plugin before 10.0.10 does not perform a capability check in one of its select2 query AJAX handlers, only verifying that the user is logged in, allowing any authenticated user with subscriber-level access to read the titles of internal post types such as coupon codes by supplying the post type.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-14231 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-14231 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14231 is a medium-severity missing authorization vulnerability in Unknown LifterLMS, published on 30 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-14231 exists.

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

## Sources

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

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