MPG <= 4.2.1 - Unauthenticated SQL Injection via URL Path
Strategic Overview
- Status
- Patched in 4.2.2
- Affected Version
<= 4.2.1- CVSS
- 6.5Medium
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2026-85198
At a glance
CVE-2026-85198 is a medium-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the MPG WordPress plugin, affecting versions <= 4.2.1. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 4.2.2; sites on affected versions should update now. Disclosed September 2026, reported by Nhien Pham (nhienit) (nhienit).
Vulnerability Overview
The MPG – Multiple Page Generator, Bulk Landing Pages & Programmatic SEO plugin for WordPress is vulnerable to generic SQL Injection via URL Path in all versions up to, and including, 4.2.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. This is only exploitable when the [mpg_spintax] shortcode is rendered in site-wide content such as a footer or template part, as the vulnerable code path is only reached when the shortcode is active on the requested page.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Reaching this weakness in MPG <= 4.2.1 takes no account at all. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.
A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For MPG the fix is 4.2.2: builds <= 4.2.1 are affected, anything from 4.2.2 onward is not.
Remediation
Update to version 4.2.2, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: MPG 4.2.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Same weakness class
- 7.2CVE-2023-33927: Multiple Page Generator… SQL Injection
CVE-2023-33927 - 7.2CVE-2023-2607: Multiple Page Generator Plugin <= 3.3.17 SQL Injection
CVE-2023-2607 - 6.5CVE-2024-47325: Multiple Page Generator Plugin – MPG SQL Injection
CVE-2024-47325 - 4.9CVE-2026-104953: MPG <= 4.2.2 SQL Injection
CVE-2026-104953
Other vulnerabilities in MPG – Multiple Page Generator, Bulk Landing Pages & Programmatic SEO
- 7.2CVE-2024-27951: Multiple Page Generator Plugin – MPG <= 3.4.0 RCE
CVE-2024-27951 - 6.3CVE-2022-47143: Multiple Page Generator Plugin <= 3.3.9 CSRF
CVE-2022-47143 - 6.1CVE-2026-13726: Multiple Page Generator Plugin – MPG Reflected XSS
CVE-2026-13726 - 6.1CVE-2023-33999: Freemius SDK <= 2.5.9 Reflected Cross-Site Scripting
CVE-2023-33999 - 5.4CVE-2024-10705: Multiple Page Generator Plugin – MPG <= 4.0.5 SSRF
CVE-2024-10705 - 5.4CVE-2024-7424: Multiple Page Generator Plugin Missing Authorization
CVE-2024-7424 - 5.3CVE-2026-97302: MPG Information Exposure
CVE-2026-97302 - 5.3CVE-2024-1047: ThemeIsle SDK <= Various Versions Missing Authorization
CVE-2024-1047
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C