Vulnerability in WP (WordPress plugin) (CVE-2026-108066)
Summary
Vulnerability in WP (WordPress plugin) (CVE-2026-108066). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-108066 has been found in WP (WordPress plugin).
Risk of unauthorized operations or information disclosure. CVSS score: 2.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "WP (WordPress plugin) CVE-2026-108066" on the vendor's site.
CVE-2026-108066 (WP (WordPress plugin)) — CWE-639 / CVSS v3 2.7
Attack vector: remote (network-reachable) / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-639) exists in WP (WordPress plugin).
Check the vendor advisory for the affected versions of WP (WordPress plugin).
Severity: Low (CVSS 2.7/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで WP (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web contact@wpscan.com
- web nvd.nist.gov
- web wpscan.com
- web github.com