Skip to main content
Menu
CVEs

Mang Board unauthenticated post deletion in WordPress plugin

CVE-2026-120681Published , updated

9.1CriticalCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Summary

Mang Board, a WordPress plugin, has a missing authorization check that lets anyone on the network delete board posts, including ones owned by administrators, along with their comments and file links, without logging in. The flaw can be reached remotely by unauthenticated attackers, since a nonce needed to pass the initial check is publicly visible on board listing pages.

Written by a model

Original description

The Mang Board plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.4.7. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to delete any board post — including administrator-owned content — along with its associated comments and file links. A nonce sufficient to pass the initial nonce check is publicly exposed on any board listing page, meaning no prior authentication or privileged access is required to initiate the exploit.

What to do

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-120681 (Mang Board <= 2.4.7 - Missing Authorization to Unauthenticated Arbitrary Content Deletion via 'mode' / 'comment_pid' / 'board_pid'…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-120681 (entry last updated 2026-11-20):
Affected:
- kitae-park Mang Board: through 2.4.7
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-120681 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-120681 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/9ad0f900-5c2f-41c9-87ce-55a2fab5e576?source=cve
- https://plugins.trac.wordpress.org/browser/mangboard/tags/2.4.7/api/mb-board.php#L414
- https://plugins.trac.wordpress.org/browser/mangboard/tags/2.4.7/includes/functions/func.api.php#L475
- https://plugins.trac.wordpress.org/browser/mangboard/tags/2.4.7/api/mb-board.php#L19
- https://wordpress.org/plugins/mangboard/
- https://plugins.trac.wordpress.org/browser/mangboard/tags/2.4.8/api/mb-board.php
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-120681
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-120681"}.

Affected versions

cve.now Index

34Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.1/10CVSS 9.1
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 79 if added to CISA KEV
  • Would score about 74 if CISA's SSVC rates exploitation active
  • Would score about 39 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now
  4. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  5. Record last updated

Evidence 8

Questions about CVE-2026-120681

Is CVE-2026-120681 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-120681?

Mang Board: through 2.4.7.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.