# CVE-2026-85133: WPLP Cookie Consent < 4.4.2 - Subscriber+ Missing Authorization via Multiple Settings AJAX Actions

> Authenticated subscribers can read and modify administrator scan data and plugin configuration due to missing authorization checks in AJAX actions.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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:** 9 Sep 2026
- **Updated:** 9 Sep 2026
- **Also known as:** GHSA-qcjj-jxmw-wxpg

## What is CVE-2026-85133?

CVE-2026-85133 is a medium-severity missing authorization vulnerability in Unknown WPLP Cookie Consent, published on 9 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WPLP Cookie Consent  WordPress plugin before 4.4.2 does not perform nonce or capability checks on several of its settings AJAX actions, allowing any authenticated user, such as a subscriber, to read and destroy scan data belonging to the administrator and to overwrite the WPLP Cookie Consent  WordPress plugin before 4.4.2's stored configuration.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-85133 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85133 is a medium-severity missing authorization vulnerability in Unknown WPLP Cookie Consent, published on 9 Sep 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-85133 in the wild and no public exploit code.

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

## Sources

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

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