Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach plugin endpoint unauthenticated
-
DeliveryInject script via 'data_type' parameter
-
ExploitPayload stored server-side
-
ExecutionVictim loads injected page
-
PersistScript executes in victim browser
-
ImpactHijack session or admin context
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 | Requires the Mang Board WP plugin (vendor kitae-park) to be installed and active at version 2.4.0 or earlier, with the code path handling the 'data_type' parameter reachable. Per the CVSS vector (PR:N), exploitation is unauthenticated and needs no special privileges or non-default configuration at the injection stage. The limiting factor is that the injected script only fires when a user - ideally a privileged one - later accesses the page containing the stored payload, so impact depends on a victim rendering the poisoned content; sites not running this specific plugin are entirely unaffected. |
| Impact | This is a moderate-priority issue that should be patched but does not rise to emergency status. The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N, base 7.2) describes a network-reachable, low-complexity, unauthenticated stored XSS with a scope change and low confidentiality/integrity impact - consistent with a self-propagating client-side injection in a WordPress plugin. No EPSS score, KEV listing, or POC reference is present in the input, so there is no signal of active or imminent mass exploitation; this is a high-CVSS finding without corroborating exploitation-probability data. One notable tension: the CVSS vector sets UI:N, yet the description states the payload 'executes whenever a user accesses an injected page,' which implies victim interaction (visiting the page) - the UI:N scoring reflects that no interaction is needed at the injection step, but defenders should understand that payload execution depends on a victim rendering the page. Overall this reads as a genuine but bounded web-app vulnerability whose real-world urgency is tempered by the plugin's limited deployment footprint rather than by any weakness in the vulnerability itself. |
| Exploit ScenarioDerived | An unauthenticated attacker submits a crafted value in the 'data_type' parameter that is stored by the Mang Board WP plugin and later rendered into a page without proper sanitization or output escaping. When any user - including an administrator - subsequently views the affected page, the attacker's JavaScript executes in that user's browser session, enabling session/cookie theft or actions in the victim's authenticated context. No public exploit code is identified in the provided data, though the vendor patch changeset reveals the vulnerable code path. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 15, 2026
Stored cross-site scripting in Mang Board WP 2.4.0 and earlier allows unauthenticated remote attackers to inject arbitrary web scripts through the 'data_type' parameter, with execution occurring when a victim later views the poisoned page. The issue affects WordPress sites that have the kitae-park Mang Board WP plugin active and reachable on the vulnerable API/code path; sites not running the plugin are unaffected. No public exploit code or CISA KEV entry is identified at time of analysis, and the CVSS 3.1 score of 7.2 reflects a moderate-priority issue that should be patched but does not rise to emergency status.
RemediationAI
Apply the upstream fix as soon as a patched Mang Board WP release after 2.4.0 is available from the WordPress plugin repository; the provided data points to the fix in changeset 3690677 (trunk/includes/functions/func.api.php), which is best treated as upstream fix available (PR/commit); released patched version not independently confirmed. If an update cannot be applied immediately, deactivate and remove the Mang Board WP plugin if board functionality is not required, or restrict access to the affected API/code path and the 'data_type' parameter handling to trusted users/IPs, accepting that this may break legitimate board API calls. Additional compensating controls include deploying a WAF rule to block script-bearing payloads in the 'data_type' parameter and reviewing existing board content for stored script injections, with the usual trade-off of false positives and potential disruption to legitimate content; monitor the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/88d62d58-9d06-4a48-b76e-0265892107dc?source=cve and Trac changeset at https://plugins.trac.wordpress.org/changeset/3690677/mangboard/trunk/includes/functions/func.api.php for the patched release.
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
Root cause is CWE-79 (improper neutralization of input during web page generation), specifically stored XSS in the Mang Board WP WordPress plugin. The vulnerable code path is in includes/functions/func.api.php, where the 'data_type' parameter is accepted without sufficient input sanitization and later rendered without adequate output escaping; the CPE cpe:2.3:a:kitae-park:mang_board:*:*:*:*:*:*:*:* identifies the affected product line, and the description limits vulnerable versions to 2.4.0 and earlier. CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N indicates network-reachable, low-complexity exploitation with no privileges required (PR:N), but the scope-change and low confidentiality/integrity impact match script execution in a victim's browser rather than direct server compromise. Wordfence reported the flaw, and the referenced Trac changeset 3690677 in trunk/includes/functions/func.api.php is the upstream fix location, though a separately tagged fixed plugin release is not confirmed in the provided data.
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 network-reachable stored XSS (AV:N/AC:L/PR:N); scope change (S:C) as the payload executes in a victim browser, with low C and I impact and no availability effect.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Mang Board WP plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'data_type' parameter in all versions up to, and including, 2.4.0 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.
Executive ViewAI
Mang Board WP plugin versions 2.4.0 and earlier, used on WordPress sites, contain a stored cross-site scripting flaw that can allow malicious scripts to be injected and later executed when victims view poisoned pages. This can lead to session theft, credential compromise, malicious redirects, or reputational damage on affected public-facing websites, so leadership should care about any business-critical or customer-facing WordPress properties running the plugin. No vendor-released patch identified at time of analysis and no public exploit identified at time of analysis, but affected sites remain exposed until mitigated.
No vendor-released patch identified at time of analysis. Interim mitigations include deactivating or removing the kitae-park Mang Board WP plugin versions 2.4.0 and earlier, blocking or sanitizing the data_type parameter at the WAF or reverse proxy, restricting access to vulnerable API/code paths, applying Content Security Policy, enforcing MFA and least privilege for WordPress administrators, and monitoring logs and databases for injected scripts.
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
Unauthenticated stored cross-site scripting in the Mang Board plugin for WordPress (all versions up to and including 2.4
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-101845
GHSA-mgxx-8mqr-7h76
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB