# CVE-2026-108066: WP 2FA < 4.2.0 - Admin+ Arbitrary User 2FA Removal via IDOR

> Site administrators on WordPress Multisite can remove two-factor authentication for users outside their own site due to missing object-level capability checks.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-pxwp-79fp-hgfv

## What is CVE-2026-108066?

CVE-2026-108066 is a low-severity missing authorization vulnerability in Unknown WP 2FA, published on 14 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The WP 2FA  WordPress plugin before 4.2.0 does not perform an object-level capability check before removing a user's two-factor authentication configuration, allowing a site administrator on WordPress Multisite to remove the 2FA configuration of users outside their own site, including accounts they are not permitted to edit. On single-site installs an administrator can already manage all users, so this crosses a trust boundary only on Multisite.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-108066 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108066 is a low-severity missing authorization vulnerability in Unknown WP 2FA, published on 14 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-108066 in the wild and no public exploit code.

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

## Sources

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

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