Skip to main content
Menu
CVEs

Mang Board arbitrary file deletion via path traversal in file_path

Affects Mang Board 2.4.8 and earlier when an admin-created level-10 member has zero logins and their user ID is exposed externally; the checked facts name no fixed version.

CVE-2026-125059Published , updated

7.5HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Summary

The Mang Board plugin for WordPress has a path traversal flaw that lets an attacker delete arbitrary files on the server, including wp-config. The attacker can reach it remotely, without logging in, by supplying a crafted `file_path` value.

Written by a model

Original description

The Mang Board plugin for WordPress is vulnerable to Arbitrary File Deletion via Path Traversal in versions up to, and including, 2.4.8 via the file_path column handled by the mbw_board_files_api_body() function. The plugin stores an attacker-supplied value directly into the files admin table (no realpath, dot-segment, or directory-containment filtering) and later concatenates it onto MBW_UPLOAD_PATH before passing the result to @unlink(). This makes it possible for unauthenticated attackers to delete arbitrary files on the affected site's server, including `wp-config.

Who should check

Sites running the Mang Board WordPress plugin that have level-10 members created in its member management page.

“관리자>MangBoard>회원관리 페이지에서 레벨10 회원등록 + 로그인 0회 + 아이디 외부 노출(임의 대입) 3가지 조건을 모두 만족할 경우에 업로드 파일 삭제 취약점으로 이용 가능”

wordpress.org

What to do

Workaround: While no fix is listed, review the level-10 members in Member Management and remove any with zero logins that are not needed. Also keep user IDs from being exposed externally, since the issue needs all three conditions to hold.

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-125059 (Mang Board <= 2.4.8 - Unauthenticated Arbitrary File Deletion via Path Traversal via 'file_path' Parameter), 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-125059 (entry last updated 2026-11-20):
Affected:
- kitae-park Mang Board: through 2.4.8
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Mang Board admin member management has a level-10 member registered, with zero logins, and the user ID exposed externally; all three must hold for the file deletion issue (source: https://wordpress.org/plugins/mangboard/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-125059 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125059 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/00f15df1-37c5-4dff-9c9d-c227dcd139ba?source=cve
- https://plugins.trac.wordpress.org/browser/mangboard/tags/2.4.8/models/admin/files.php#L90
- https://plugins.trac.wordpress.org/browser/mangboard/tags/2.4.8/models/admin/files.php#L87
- https://plugins.trac.wordpress.org/browser/mangboard/tags/2.4.8/includes/functions/func.api.php#L152
- https://plugins.trac.wordpress.org/browser/mangboard/tags/2.4.8/api/mb-board.php#L330
- https://plugins.trac.wordpress.org/browser/mangboard/tags/2.4.8/includes/functions/func.board.php#L1703
- https://wordpress.org/plugins/mangboard/
- https://plugins.trac.wordpress.org/changeset/3806523/mangboard/trunk/models/admin/files.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-125059
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-125059"}.

Affected versions

cve.now Index

33Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.5/10CVSS 7.5
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 78 if added to CISA KEV
  • Would score about 73 if CISA's SSVC rates exploitation active
  • Would score about 38 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

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

  4. Record last updated

Evidence 10

Questions about CVE-2026-125059

Is CVE-2026-125059 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

What does this mean?

The flaw is a path traversal in the file_path parameter that can delete uploaded files on the site. It is reachable without logging in.

Source: wordpress.org

Which versions are affected by CVE-2026-125059?

Mang Board: through 2.4.8.

Source: cve.now feed data

Am I affected, and how do I check?

Mang Board 2.4.8 and earlier are listed as affected. The file deletion issue requires all three conditions: a level-10 member registered in the admin member management page, that member having zero logins, and the user ID being exposed externally. Check the version in the product and the member list under Admin > MangBoard > Member Management.

Source: wordpress.org

How do I fix CVE-2026-125059?

The checked facts name no fixed version or vendor patch, so check the vendor's source for an update before relying on any release.

Source: wordpress.org

What if there's no patch?

While no fix is listed, review the level-10 members in Member Management and remove any with zero logins that are not needed. Also keep user IDs from being exposed externally, since the issue needs all three conditions to hold.

Source: wordpress.org

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