---
id: "CVE-2026-109512"
kind: "vulnerability"
aliases: ["CVE-2026-109512"]
title: "WordPress Mang Board plugin: stored XSS through the content parameter"
severity: "medium"
cvss: 6.4
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "php", "self-hosted", "wordpress"]
not_affected_if: ["no-subscriber-accounts", "patched-version", "plugin-not-installed"]
published_at: "2026-10-16T05:17:29+00:00"
first_seen_at: "2026-10-23T21:57:12+00:00"
updated_at: "2026-10-25T03:59:58+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-109512", "first_seen_at": "2026-10-23T21:57:12+00:00"}]
---

# WordPress Mang Board plugin: stored XSS through the content parameter

The Mang Board plugin for WordPress lets a logged-in subscriber store script in the content parameter, because input is not sanitized and output is not escaped. The injected script runs in the browser of anyone who opens the affected page, including administrators.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check whether the Mang Board plugin is installed and its version, in the WordPress admin under Plugins, or with `wp plugin get mang-board --field=version` (plugin slug assumed; confirm in the sources)
- unknown

## Fix

- Update the Mang Board plugin to a version later than `2.4.4`, if the vendor has released one (the sources do not name a fixed version)
- If no fixed version exists, deactivate the plugin or restrict subscriber accounts until it is patched

## Timeline

- 2026-10-23T21:57:12+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-109512

## From the sources

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.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The sanitization bypass is further compounded by the ability to omit the data_type parameter in a modify request, which skips the HTMLPurifier branch entirely and leaves only mbw_htmlspecialchars2 encoding — fully reversed at render — as the sole barrier.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_