Privilege Escalation in Mang Board WP (WordPress plugin) (CVE-2026-75977)
Summary
Vulnerability in Mang Board WP (WordPress plugin) (CVE-2026-75977). Successful exploitation can lead to full system takeover.
Original description
The description as published by the source.
The Mang Board WP plugin for WordPress is vulnerable to Missing Authorization via Authentication Cookie Forgery in all versions up to, and including, 2.3.7. This is due to flawed HMAC generation in the mbw_get_hash_key() function that uses the current user's identity instead of the cookie username parameter when a WordPress user is logged in, combined with insufficient validation in mbw_validate_auth_cookie(). This makes it possible for authenticated attackers, with subscriber-level access and above, to forge administrator authentication cookies and change administrator passwords to achieve complete site takeover.
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-75977 has been found in Mang Board WP (WordPress plugin).
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Mang Board WP (WordPress plugin) CVE-2026-75977" on the vendor's site.
CVE-2026-75977 (Mang Board WP (WordPress plugin)) — CWE-269 / CVSS v3 8.8
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-269) exists in Mang Board WP (WordPress plugin).
Check the vendor advisory for the affected versions of Mang Board WP (WordPress plugin).
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
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・依存マニフェストで Mang Board WP (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web plugins.trac.wordpress.org
- web plugins.trac.wordpress.org
- web plugins.trac.wordpress.org
- web plugins.trac.wordpress.org
- web plugins.trac.wordpress.org
- web plugins.trac.wordpress.org
- web plugins.trac.wordpress.org
- web plugins.trac.wordpress.org
- web plugins.trac.wordpress.org
- web plugins.trac.wordpress.org
- web security@wordfence.com
- web wordfence.com
- web nvd.nist.gov
- web plugins.trac.wordpress.org
- web github.com