Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach public admin-ajax.php endpoint
-
DeliverySend crafted content_reply request
-
ExploitBypass nonce and inject script in 'content'
-
ExecutionPayload stored and served as text/html
-
ImpactVictim views page, script executes in browser
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 | No special conditions beyond having the Mang Board plugin (≤2.4.3) installed and active: the wp_ajax_nopriv_mb_template endpoint is exposed to unauthenticated users by default, nonce verification is not enforced for the content_reply mode, and admin-ajax.php returns Content-Type: text/html which causes browsers to execute injected tags in the JSON response body. The main limiting factor is that this is stored XSS - the payload only executes when a user subsequently accesses the injected page, so impact depends on a victim (ideally a privileged one) viewing the affected content; no authentication, user interaction at injection time, or non-default configuration is required. |
| Impact | This is a genuine, elevated-priority issue for sites running the Mang Board plugin, though not a top-tier emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C) describes a network-reachable, low-complexity, fully unauthenticated attack with no user interaction and a changed scope - an unusually favorable profile for an attacker, which is why a 'low/low' impact XSS still reaches 7.2. The description substantiates the PR:N claim with a concrete mechanism: the wp_ajax_nopriv_mb_template endpoint is public, nonce verification is skipped for content_reply mode, and admin-ajax.php returns Content-Type: text/html, so injected markup in the JSON body actually executes. No EPSS score, CISA KEV listing, or public POC was provided in the input, so there is no signal of active or automated exploitation - this appears to be a newly disclosed Wordfence-reported flaw rather than one under mass attack. The practical ceiling on impact is that this is stored XSS (C:L/I:L/A:N): it compromises sessions/content in the victim's browser context rather than directly yielding server code execution. Net: a real, easily-triggerable vulnerability worth prompt patching, but current exploitation evidence is absent and real-world blast radius is bounded by the limited product footprint. |
| Exploit ScenarioDerived | An unauthenticated attacker sends a crafted request to admin-ajax.php invoking the wp_ajax_nopriv_mb_template action in content_reply mode, placing a malicious script into the 'content' parameter that bypasses nonce checks and sanitization. Because the response is served as text/html, the stored payload later executes in the browser of any user - including an administrator - who views the injected page, enabling session theft or actions in that user's context. No public exploit code was identified at time of analysis, but the attack path is fully documented in the advisory and trivially reproducible. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 16, 2026
Stored cross-site scripting in the Mang Board WordPress plugin (all versions up to and including 2.4.3) lets unauthenticated attackers inject arbitrary JavaScript that executes in the browser of any user who later loads the poisoned board content. The injection path is unusually easy because the wp_ajax_nopriv_mb_template endpoint is publicly reachable, nonce verification is not enforced in content_reply mode, and admin-ajax.php answers with Content-Type: text/html so script tags embedded in the JSON body are parsed and executed. Wordfence rates it CVSS 7.2 (scope changed, PR:N/UI:N) and an upstream fix commit is referenced in the plugin's Trac changeset, but no public exploit code has been identified at time of analysis and there is no confirmed active exploitation, so this is an elevated-priority, patch-now issue rather than a top-tier emergency - the residual constraint is that execution requires a victim, ideally a privileged one, to view the injected page.
RemediationAI
Upstream fix available (PR/commit); released patched version not independently confirmed, so the immediate action is to review the vendor changeset at https://plugins.trac.wordpress.org/changeset?reponame=&old=3738899%40mangboard&new=3738899%40mangboard, confirm whether a tagged stable release carrying it has been published, and update the plugin to that release (or remove it) as soon as it is available. If no patched build can be applied yet, deactivate Mang Board entirely - the cleanest fix with the only real trade-off being loss of the board/template functionality. Alternatively, block unauthenticated access to the vulnerable action by hooking remove_action on the wp_ajax_nopriv_mb_template registration through a small mu-plugin, accepting that logged-out template and reply features will stop working. A WAF rule that rejects requests to wp-admin/admin-ajax.php with an mb_template action whose parameters contain angle brackets or script syntax will blunt exploitation but risks false positives on legitimate markup, and it does not repair already-stored payloads. Additional compensating controls include enforcing a nonce check and output escaping in the content_reply path, sanitizing and reviewing existing board content for stored payloads, and restricting who can view board pages until patched. Regardless of the mitigation chosen, keeping the plugin current and monitoring the Wordfence advisory for an updated fixed version is essential, since stored XSS of this kind is typically leveraged to hijack administrator sessions and plant further backdoors.
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
The root cause is CWE-79, improper neutralization of input during web page generation, inside a PHP-based WordPress plugin. Mang Board registers an AJAX action named mb_template through wp_ajax_nopriv_mb_template, which WordPress exposes to unauthenticated callers via wp-admin/admin-ajax.php. In the content_reply mode the handler neither validates a nonce nor sanitizes the supplied 'content' parameter before persisting it, and the value is later emitted without output escaping. The exploit is compounded by the response handling: admin-ajax.php returns Content-Type: text/html rather than application/json, so any HTML or script tags echoed inside the JSON response body are treated as markup and executed by the browser, giving an attacker a direct execution primitive in addition to the persisted stored-XSS payload. The CPE cpe:2.3:a:kitae-park:mang_board points to the kitae-park distribution of the plugin, and the vulnerable logic is visible in api/mb-template.php (around lines 150 and 177), api/mb-board.php (line 24) and includes/functions/func.api.php (line 146) at the 2.4.3 tag. The assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N confirms the attack is network-reachable, low complexity, requires no privileges and no user interaction at injection time, with the scope change reflecting the script executing in the victim's browser session rather than the server context.
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
Public nopriv endpoint with no nonce gives AV:N/AC:L/PR:N/UI:N; stored XSS executing in a separate browser context gives S:C with C:L/I:L and no availability impact.
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 'content' parameter in all versions up to, and including, 2.4.3 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 because the wp_ajax_nopriv_mb_template endpoint is publicly accessible without authentication, nonce verification is not enforced for the content_reply mode, and admin-ajax.php responds with Content-Type: text/html, causing browsers to execute injected tags embedded in the JSON response body.
Executive ViewAI
The Mang Board WordPress plugin, in all versions up to and including 2.4.3, contains a stored cross-site scripting issue that can be injected without authentication and then executed when users view affected board content. Because successful exploitation can compromise privileged WordPress sessions and potentially lead to broader site or administrative control, leadership should treat this as a high-priority remediation item; however, there is no public exploit identified at time of analysis and no confirmed active exploitation. Organizations running this plugin should immediately assess exposure and remove or mitigate it until a vendor patch is available.
No vendor-released patch identified at time of analysis; interim mitigations include disabling or removing the Mang Board plugin (all versions up to and including 2.4.3), blocking or virtually patching the wp_ajax_nopriv_mb_template action and content_reply mode at the WAF/reverse proxy, restricting or monitoring access to admin-ajax.php, and reviewing board content for injected JavaScript until a vendor fix is available.
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
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 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-102647
GHSA-whj8-6p7v-qjm7
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB