Skip to main content

Mang Board WP CVE-2026-109698

| EUVDEUVD-2026-102028 CRITICAL
SQL Injection (CWE-89)
2026-10-15 Patchstack GHSA-hm79-79jw-89mp
9.3
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify site running Mang Board WP
  2. Exploit
    Send crafted request with SQL payload
  3. Execution
    Injection executes in database query
  4. Impact
    Extract sensitive database contents

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

The target must be running the Mang Board WP plugin at version 2.4.4 or earlier (fixed version not stated in available data). The description does not name the specific vulnerable parameter, endpoint, or feature, so the exact injection point is unconfirmed. Per the provided CVSS vector (PR:N/UI:N), no authentication or user interaction is claimed to be required, which would allow remote unauthenticated exploitation; however, this privilege rating is unusually permissive for a WordPress plugin SQLi and is not corroborated by the description text, so defenders should verify whether some authenticated role (e.g., Subscriber) is actually required before deprioritizing based on auth. No non-default configuration is indicated as a prerequisite.

Impact

The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L, score 9.3) describes a network-reachable, low-complexity, unauthenticated SQL injection (CWE-89) with a scope change and high confidentiality impact - on paper a critical-priority issue. However, the real-world signals temper this: there is no EPSS score provided, no CISA KEV listing, and no public proof-of-concept referenced, so there is no public exploit identified at time of analysis. The single source is a Patchstack advisory, which is a credible vulnerability-research vendor but represents one source rather than confirmed field exploitation. Two points warrant verification: (1) the PR:N (unauthenticated) rating is unusually generous for a WordPress plugin SQLi - many Patchstack-reported plugin SQLi flaws actually require at least Subscriber/authenticated access, and the terse description ('allows SQL Injection') does not confirm the privilege level, so verify the required authentication with the Patchstack advisory; (2) the I:N/A:L with C:H combination is atypical for SQLi, which usually yields high confidentiality impact only - the A:L and S:C warrant scrutiny. Net: credible high-severity flaw worth prompt patching for anyone running the plugin, but widespread opportunistic exploitation is not yet evidenced, and the deployment footprint is small.

Exploit ScenarioDerived

A remote attacker sends a crafted HTTP request to a vulnerable Mang Board WP endpoint, injecting SQL through an improperly neutralized parameter to read sensitive data from the WordPress database (e.g., user records, password hashes, session/secret data). The CVSS vector indicates network-based, low-complexity exploitation requiring no user interaction; no public proof-of-concept is referenced, so exploitation would currently require an attacker to independently develop the injection payload.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 15, 2026

SQL injection in the Mang Board WP WordPress plugin (Kitae Park) affects all versions through 2.4.4 and lets an attacker inject arbitrary SQL into the site's backend database queries, with the primary impact being high confidentiality loss (bulk read of user records, password hashes, and other stored data) plus a limited integrity effect. The vendor/Patchstack vector advertises a 9.3 score with scope change and no privileges required (PR:N/UI:N), but the independent assessment rates the issue as PR:L with unchanged scope (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N), so the authentication requirement should be treated as unconfirmed - the PR:N rating in the published vector is unusually permissive for a WordPress plugin SQLi and is not corroborated by the description text, which names no vulnerable parameter, endpoint, or feature. Only a Patchstack database entry is available: no vendor patch version is stated and no public exploit code has been identified at time of analysis.

RemediationAI

No vendor-released patch version is identified in the available data, so the primary action is to check the plugin's WordPress.org page and the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/mangboard/vulnerability/wordpress-mang-board-wp-plugin-2-4-4-sql-injection-vulnerability?_s_id=cve) for a release above 2.4.4 and upgrade to the first patched version as soon as it is published - do not assume 2.4.5 is the fix unless the changelog confirms it. If the plugin is not essential, deactivating and removing it eliminates the exposure entirely, at the cost of losing the board functionality and any content it rendered. If it must stay live pending a patch, take the following compensating controls with their trade-offs: deploy a WAF rule set in front of the plugin's endpoints and admin-ajax.php actions to block SQL metacharacters and known injection patterns (effective only against known payloads, and may generate false positives on legitimate board content); since the authentication requirement is ambiguous, temporarily restrict access to the plugin's front-end routes so that only logged-in users, or only trusted roles, can reach them (this changes site behavior and breaks public/guest board access); disable any guest-posting or anonymous submission features that expose unauthenticated input to the plugin (this is the highest-value hardening step if PR:N turns out to be correct); and enforce least privilege on the WordPress database user to blunt the impact of any successful read. Because an injection can dump credential material, plan a post-mitigation review of wp_users and plugin-stored data for signs of exfiltration, and rotate database and administrative passwords if you find evidence of successful exploitation. Continue to treat authentication requirements as unconfirmed until the vulnerable parameter is published.

Affected VersionsENISA

Mang Board WP 0 ≤2.4.4

Affected Packages

euvd mang_board_wp no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-89, Improper Neutralization of Special Elements used in an SQL Command: the plugin builds database queries by concatenating user-controllable input instead of using parameterized queries or prepared statements, so attacker-supplied characters can break out of the intended SQL context and alter query semantics. Mang Board WP is a WordPress plugin (CPE cpe:2.3:a:kitae_park:mang_board_wp:*:*:*:*:*:*:*:*), meaning it executes inside the WordPress/PHP stack against the site's MySQL/MariaDB database and inherits the database privileges of wp-config.php; any successful injection therefore grants the attacker whatever read/write surface that database account holds. The published vector claims S:C (scope change), which in CVSS terms implies the vulnerable component could affect resources beyond its own security authority; the independent assessment retains S:U, so the cross-boundary impact should not be assumed. The specific injection point - parameter, shortcode, AJAX action, or board field - is not identified in the available data, and the mechanism most likely involves an unescaped request parameter reaching a dynamically constructed query. Because WordPress plugin SQLi is typically prelude to credential theft and privilege escalation within the CMS, the confidentiality weighting (C:H) is the most consequential element of this finding.

Know when Mang Board Wp gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 9.3 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
vuln.today AI 7.1 HIGH

SQLi is network-exploitable and low-complexity; most WordPress plugin SQLi require at least low-privilege authentication (PR:L), primarily leak data (C:H) with limited write (I:L) and no scope change absent evidence.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

DescriptionCVE.org

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Kitae Park Mang Board WP mangboard allows SQL Injection.This issue affects Mang Board WP: from n/a through 2.4.4.

Executive ViewAI

Why It Matters

Mang Board WP WordPress plugin versions through 2.4.4 contain a critical SQL injection vulnerability that can expose user records, password hashes, and other stored data. No vendor-released patch identified at time of analysis and no public exploit identified at time of analysis, and the authentication requirement is unconfirmed. Leadership should prioritize discovery and containment across affected WordPress sites because a successful attack could lead to credential compromise, regulatory exposure, and reputational harm.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include disabling or removing the Mang Board WP plugin (all versions through 2.4.4) until a fixed version is available; restricting administrative access; deploying WAF/virtual patching rules to block SQL injection attempts; monitoring database and web logs for suspicious queries; and rotating credentials if exposure is suspected.

Threat Intelligence Overview

EPSS Score
0.3%
Top 80% exploitable
Prevalence
Low
niche Korean bulletin-board WordPress plugin, limited global footprint
Social Media
3
Sightings
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +46
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy