# CVE-2026-109219: Mang Board - 2.4.4 - Unauthenticated Arbitrary File Upload via 'image_path' Parameter

> Unauthenticated attackers can upload executable files via the image_path parameter in Mang Board, leading to remote code execution.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-rr8c-wv2m-x2qx

## What is CVE-2026-109219?

CVE-2026-109219 is a critical vulnerability in kitae-park Mang Board, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2026-109219?


## How do I fix CVE-2026-109219?

No fix has been published for CVE-2026-109219 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-109219 being exploited?

There is no known exploitation of CVE-2026-109219 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-109219 and fix it if it is affected.

What it is: CVE-2026-109219 is a critical vulnerability in kitae-park Mang Board, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-109219 in the wild and no public exploit code.

Affected product: kitae-park Mang Board. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-109219/ (Markdown: https://insights.sbomify.com/CVE-2026-109219/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-109219
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-109219
- OSV: https://osv.dev/vulnerability/CVE-2026-109219

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-109219/
Summaries are generated and may contain mistakes; the official description above is the record.