Live › vulnerability › CVE-2026-109219
Go to dashboardMang Board <= 2.4.4 (WordPress plugin, slug mangboard) lets unauthenticated visitors upload arbitrary files, including PHP, via mbw_file_upload. The image_path parameter bypasses the extension allowlist that only covers file_name. Exploitation needs guest posts enabled, which is the default. The nonce is printed on every public board page, so no login is needed. CVSS 9.8, reported by Osman Hussein via Wordfence, published 2026-10-15. Remote code execution on the web server is possible. No known exploitation or public PoC yet.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|
| Mang Board (mangboard) | wordpress | <= 2.4.4 | 2.4.5 |
2.4.4 is vulnerable2.4.5 or later; wp.org currently ships 2.4.6 (wp plugin update mangboard)2.5.6 (2.4.5)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The Mang Board plugin for WordPress is vulnerable to Arbitrary File Upload in version 2.4.4 via the mbw_file_upload function. This is due to missing file extension validation on the attacker-supplied image_path parameter, whose basename-derived file name bypasses the extension allowlist applied only to the separate file_name parameter. This makes it possible for unauthenticated attackers to upload files that may be executable, which makes remote code execution possible. Exploitation requires the board to be configured to allow guest posts, which is the plugin's default mode; the required nonce is printed on every public board page, making it readable by any unauthenticated visitor without a WordPress login.
This page as .md · .json · in your agent: get_signal("CVE-2026-109219")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.