Skip to main content

Mang Board WP EUVDEUVD-2026-66335

| CVE-2026-75977 HIGH
Improper Privilege Management (CWE-269)
2026-08-26 Wordfence GHSA-fwqj-5r7m-j49j
8.8
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Obtain subscriber-level WordPress account
  2. Delivery
    Authenticate to target site with Mang Board WP ≤ 2.3.7 active
  3. Exploit
    Analyze plugin source to understand HMAC flaw in mbw_get_hash_key()
  4. Install
    Craft forged admin-identity cookie using subscriber session HMAC material
  5. C2
    Submit forged cookie to bypass mbw_validate_auth_cookie()
  6. Execute
    Change administrator password via users.php admin endpoint
  7. Impact
    Achieve full WordPress site takeover

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the attacker to hold a valid WordPress account at subscriber level or above on the target site - unauthenticated exploitation is not possible per the CVSS PR:L vector. The Mang Board WP plugin must be installed and active, and the victim site must expose the plugin's custom cookie validation flow (which activates when the plugin's board or user functionality is in use, as evidenced by the affected code paths in func.board.php, func.user.php, and mb-template.php). No other non-default configuration is required beyond plugin activation and a subscriber-level account. The primary limiting factor is the authentication prerequisite: sites that disable open user registration and restrict all accounts to trusted individuals significantly reduce their exposure, since exploitation then requires either a malicious insider or a pre-existing account compromise. There is no requirement for specific operating system, hosting platform, or WordPress version beyond plugin activation.

Impact

The CVSS 8.8 High vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) accurately models this vulnerability. The single meaningful friction point is PR:L - an attacker must hold at minimum a subscriber-level WordPress account on the target site, which on sites with open registration may be trivially obtained. Attack complexity is genuinely low: exploiting the flaw requires understanding the HMAC generation logic (derivable from the publicly browsable Trac source code), crafting a cookie, and submitting it. No EPSS data was provided in the input; KEV status is negative and no public exploit code has been identified at time of analysis, suggesting this has not yet seen opportunistic mass exploitation. However, the Wordfence disclosure and multiple source-code-level references substantially lower the barrier to independent exploit development. Sites permitting open user registration or hosting any untrusted authenticated users are at elevated practical risk. The full C:H/I:H/A:H impact reflects that admin-level access over a WordPress site constitutes complete control: content modification, credential harvesting, webshell installation, and full availability disruption are all within reach post-exploitation.

Exploit ScenarioDerived

An attacker registers a free subscriber account on a WordPress site running Mang Board WP ≤ 2.3.7, or compromises an existing low-privilege account. While authenticated as a subscriber, the attacker leverages the publicly browsable plugin source code to understand the flawed HMAC construction in mbw_get_hash_key(), then crafts a custom authentication cookie that names the site administrator as its subject but signs it using HMAC material derived from the attacker's own active session. Submitting this forged cookie causes mbw_validate_auth_cookie() to grant administrator-level access, at which point the attacker changes the administrator password and installs a backdoor for persistent control of the site.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.6% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 26, 2026

Cookie forgery in the Mang Board WP WordPress plugin (≤2.3.7) enables any subscriber-level account holder to forge administrator authentication cookies and change the administrator password, resulting in complete WordPress site takeover. The flaw originates in mbw_get_hash_key(), which generates HMAC material from the currently logged-in user's identity rather than the username embedded in the cookie under validation, while mbw_validate_auth_cookie() performs insufficient verification - allowing the forged cookie to pass as legitimate. No public exploit has been identified at time of analysis and no CISA KEV listing is present, but the CVSS 8.8 score accurately reflects the low privilege bar required and full confidentiality, integrity, and availability impact.

RemediationAI

Update the Mang Board WP plugin to the first release after version 2.3.7, as the upstream fix is represented by WordPress Plugin Trac changeset 3664567 (https://plugins.trac.wordpress.org/changeset/3664567/); however, the exact patched release version number is not independently confirmed from available data and should be verified against the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/ae75196d-2128-4da8-a90b-a62454dcdbe9 before deploying. As an immediate compensating control pending patching, disable open WordPress user registration (Settings → General → uncheck 'Anyone can register') to prevent untrusted parties from obtaining subscriber-level accounts - note this will block self-service enrollment for legitimate new users. Additionally, audit existing subscriber and contributor accounts for unexpected privilege escalation, including unauthorized changes to administrator passwords or email addresses. Sites that cannot patch immediately should consider temporarily deactivating the Mang Board WP plugin, accepting loss of its board functionality, to eliminate the attack surface entirely.

Affected VersionsENISA

Mang Board WP 0 ≤2.3.7

Affected Packages

euvd mang_board_wp no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The Mang Board WP plugin (CPE: cpe:2.3:a:kitae-park:mang_board_wp:*:*:*:*:*:*:*:*) implements its own HMAC-based custom authentication cookie system, separate from WordPress core session handling. The vulnerable function mbw_get_hash_key() (func.board.php:L32 and func.board.php:L1581) constructs the HMAC signing key using the identity of the currently active WordPress session rather than extracting the username from the cookie being validated. This means a subscriber authenticating to the site can generate a structurally valid HMAC for a cookie that names the administrator as its subject. The companion function mbw_validate_auth_cookie() (func.user.php:L447 and mb-template.php:L36) then accepts this forged cookie because the HMAC check passes - it is signed with the subscriber's key material but validated against the same. The downstream impact path runs through users.php:L125, where the authenticated session identity is used to authorize password-change operations. CWE-269 (Improper Privilege Management) captures the root cause: the plugin fails to enforce privilege boundaries during cookie validation, enabling horizontal-to-vertical privilege escalation from subscriber to administrator.

Know when Mang Board Wp gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Wordfence) PRIMARY 8.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

Network-exploitable with low complexity; PR:L reflects mandatory subscriber authentication; full CIA impact from complete WordPress admin takeover.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

The Mang Board WP WordPress plugin (versions 2.3.7 and earlier) allows subscriber-level accounts to forge administrator credentials and achieve complete WordPress site takeover. While no public exploit identified at time of analysis, the absence of vendor-released patches creates urgent risk for any organization using this plugin. Immediate plugin removal is critical to prevent unauthorized administrative access, data breach, and operational compromise.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) immediately disable and uninstall the vulnerable plugin; (2) restrict subscriber user role access to essential functions only; (3) implement multi-factor authentication for all administrator accounts; (4) enable comprehensive authentication and user activity logging to detect unauthorized access attempts; (5) enforce strong password policies and enforce immediate password resets for all administrative users. Complete plugin removal is the most effective control pending vendor remediation.

Threat Intelligence Overview

EPSS Score
0.6%
Top 53% exploitable
Prevalence
Low
niche WordPress board plugin, limited global deployment footprint
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.6%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

45
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy