# CVE-2026-18046: Cookie Consent < 0.0.10 - Subscriber+ MaxMind License Key Update

> Authenticated users can overwrite the geolocation license key due to missing authorization checks, disrupting consent banner targeting.

- **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:** 12 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-xcj8-382p-cc46

## What is CVE-2026-18046?

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

### Official description

The Cookie Consent  WordPress plugin before 0.0.10 does not correctly enforce its intended administrator-only capability check on the REST route that stores its geolocation service license key, so the route falls back to an authentication-only gate, allowing any authenticated user such as a subscriber to overwrite the stored key and disrupt the Cookie Consent  WordPress plugin before 0.0.10's geolocation-based consent banner targeting.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-18046 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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