# CVE-2026-6506: Missing authorization in InfusedWoo Pro

> Authenticated subscribers can escalate privileges to Administrator by updating user meta due to missing authorization checks in InfusedWoo Pro.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 14 May 2026
- **Updated:** 14 May 2026
- **Also known as:** GHSA-46r5-fg25-pxgj

## What is CVE-2026-6506?

CVE-2026-6506 is a high-severity missing authorization vulnerability in InfusedWoo Pro, published on 14 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The InfusedWoo Pro plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 5.1.2. This is due to the infusedwoo_gdpr_upddata() function missing authorization and capability checks, as well as lacking restrictions on which user meta keys can be updated. This makes it possible for authenticated attackers, with subscriber-level access and above, to update their own wp_capabilities user meta to grant themselves Administrator role privileges.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-6506 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6506 is a high-severity missing authorization vulnerability in InfusedWoo Pro, published on 14 May 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-6506 in the wild and no public exploit code.

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

## Sources

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

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