Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach public board page
-
DeliverySubmit post with crafted 'data_type' payload
-
ExploitScript stored without sanitization
-
ExecutionAdmin or user views injected page
-
PersistPayload executes in victim browser
-
ImpactSession hijack or privileged action
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitable without authentication against any board using the out-of-the-box defaults write_level=0 (guest posting enabled) and editor_type=N, which are the defaults for newly created boards - so no non-default setup is needed to be vulnerable. The specific injection point is the 'data_type' parameter, which lacks input sanitization and output escaping. Limiting factors: exploitation requires a board reachable by the attacker and still configured with guest posting (an administrator who disabled guest posting via write_level or switched editor_type away from N reduces exposure), and impact depends on a victim subsequently loading the injected page for the stored script to fire. |
| Impact | This is a genuine, elevated-priority issue for sites running the affected plugin, though not an emergency across the broader internet. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C) describes network-reachable, low-complexity, unauthenticated exploitation with a scope change - consistent with stored XSS where injected script executes in other users' browser contexts. The reinforcing signal is strong on the technical side: the description confirms exploitation works against the out-of-the-box default configuration (write_level=0 guest posting, editor_type=N), meaning no victim-side misconfiguration is required to be vulnerable. However, several real-world-risk signals are MISSING from the input and must not be fabricated: no EPSS score was provided, there is no CISA KEV listing, and no public proof-of-concept is referenced - so exploitation status is 'no public exploit identified at time of analysis.' The overall CVSS of 7.2 (High) is driven largely by PR:N plus scope change; the actual impact is limited (C:L/I:L/A:N), i.e., script injection rather than server compromise. Net: treat as a prioritized patch for sites running Mang Board, but the limited real-world deployment footprint of this niche plugin and the absence of active-exploitation evidence argue against treating it as an internet-wide incident. |
| Exploit ScenarioDerived | An unauthenticated attacker visits a public Mang Board board left at its default guest-posting settings and submits a post whose 'data_type' parameter carries a malicious script payload that is stored unsanitized. When any user - including an administrator - later views the injected board page, the script executes in their browser session, enabling session/cookie theft, forced actions, or redirection. No public exploit code is referenced in the provided data, so this scenario is inferred from the CVSS vector (network, low complexity, no privileges, no user interaction) and the stated default-configuration exposure. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 02, 2026
Unauthenticated stored cross-site scripting in the Mang Board plugin for WordPress (all versions up to and including 2.4.2) lets remote attackers inject arbitrary JavaScript through the unsanitized 'data_type' parameter, which is persisted and then executes in the browser of any user who subsequently loads the affected board page. Exploitation is possible against any board left at the plugin's out-of-the-box defaults (write_level=0 for guest posting and editor_type=N), so newly created boards are vulnerable without any special configuration; the main limiting factor is that a victim must later view the injected page for the script to fire. No public exploit code or confirmed active exploitation has been identified at time of analysis, and while the CVSS 3.1 score of 7.2 (AV:N/AC:L/PR:N/UI:N/S:C) makes this a genuine elevated-priority issue for sites running the affected plugin, it is not an emergency across the broader internet.
RemediationAI
Primary action is to update the Mang Board plugin to the first release that contains the upstream fix; the input only documents vulnerable versions through 2.4.2 and provides a Trac changeset at https://plugins.trac.wordpress.org/changeset?reponame=&old=3712357%40mangboard&new=3712357%40mangboard, which reflects an upstream fix (commit/changeset) but does not name a released patched version, so the patched release number should be confirmed against the plugin's changelog before relying on it. Until then, the most effective compensating control is to remove the vulnerable configuration: disable guest posting by raising each board's write_level above 0 (require at least a registered subscriber/contributor) and change editor_type away from N for all boards, since the flaw is only exploitable with the default guest-posting, editor_type=N combination - the trade-off is that anonymous visitors can no longer submit posts and some board workflows may need re-authoring. Administrators who cannot immediately reconfigure or upgrade should add WAF/virtual-patching rules that reject or encode script-bearing 'data_type' values on board submission endpoints, and should review existing board content for injected payloads; note that WAF filtering is bypass-prone and is a stopgap, not a substitute for the fix. Full remediation details and any updated version guidance are available in the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/8ae8d77c-cf52-442a-a273-9bca21db6e32?source=cve.
Affected VersionsENISA
Affected Packages
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
This is a classic CWE-79 improper neutralization of input during web page generation (stored/persistent cross-site scripting) affecting a WordPress plugin. The 'data_type' parameter supplied to the plugin's board-handling routines is neither sanitized on input nor escaped on output, so attacker-controlled markup is written into the site's database and rendered into board pages. The Wordfence-reported source references point at the specific handling code in the Mang Board 2.4.2 tag: includes/skin-filters.php (line 75), includes/functions/func.api.php (lines 79 and 133), and includes/mb-actions.php (line 520), plus a plugin Trac changeset that appears to address the issue. The assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N confirms the attacker is unauthenticated (PR:N), requires no user interaction to inject (UI:N), and that the impact crosses a security boundary (S:C) - a malicious script running in a victim's session can act with that user's privileges, so on a site where an administrator views the injected board, stored XSS can escalate to full site compromise. The vulnerability is a plugin-level flaw in the kitae-park:mang_board component (CPE cpe:2.3:a:kitae-park:mang_board:*), not in WordPress core, and it inherits the usual XSS risk profile of persistent injection into community/board content.
Know when Mang Board 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
AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Unauthenticated guest posting is the documented default so PR:N and AC:L; stored XSS crosses into victim browser context (S:C) with limited confidentiality/integrity impact and no availability effect.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Mang Board plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'data_type' parameter in all versions up to, and including, 2.4.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is exploitable on any board configured with the default write_level=0 (guest posting) and editor_type=N settings, which are the out-of-the-box defaults for newly created boards.
Executive ViewAI
Organizations using the Mang Board plugin for WordPress, versions up to and including 2.4.2, face a high-severity unauthenticated stored cross-site scripting vulnerability that allows attackers to inject malicious JavaScript into board pages, which then executes in the browsers of any visitor. This could lead to session hijacking, credential theft, or site defacement, impacting both site users and administrators. No public exploit identified at time of analysis, but the vulnerability poses a significant risk, particularly for sites with default board configurations that permit guest posting.
No vendor-released patch identified at time of analysis. Interim mitigations include disabling the Mang Board plugin if not essential, or if it must remain active, changing board settings to require authentication for posting (e.g., setting write_level to a value greater than 0) and avoiding default editor configurations. Deploy a web application firewall (WAF) with rules to block XSS attempts targeting the 'data_type' parameter. Regularly scan and sanitize board content for injected scripts. Monitor vendor channels for a patch release.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Mang Board
View allUnauthenticated file upload in the WordPress plugin Mang Board (all versions up to and including 2.4.4) lets an anonymou
Cross-Site Request Forgery (CSRF) vulnerability in Hometory Mang Board WP plugin <= 1.7.6 versions. Rated high severity
Unauthenticated local file inclusion in the Mang Board WordPress plugin (all versions through 2.4.3) allows remote attac
A vulnerability was found in Mangboard(WordPress plugin). Rated high severity (CVSS 7.5), this vulnerability is remotely
Stored cross-site scripting in the Mang Board WordPress plugin affects every version up to and including 2.4.3, allowing
Stored cross-site scripting in the Mang Board WordPress plugin (all versions up to and including 2.4.3) lets unauthentic
Stored cross-site scripting in Mang Board WP 2.4.0 and earlier allows unauthenticated remote attackers to inject arbitra
Stored cross-site scripting in the Mang Board plugin for WordPress (all versions up to and including 2.4.3) allows an au
Stored cross-site scripting in the Mang Board WordPress plugin (versions up to and including 2.4.4) allows authenticated
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Hometory Mang Boar
EUVD-2026-91251
GHSA-7fq9-mp55-2j96
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB