Multiple Page Generator Plugin <= 3.3.17 - Cross-Site Request Forgery to SQL Injection
Strategic Overview
- Status
- Patched in 3.3.18
- Affected Version
<= 3.3.17- CVSS
- 3.1Low
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2023-2608
At a glance
CVE-2023-2608 is a low-severity Cross-Site Request Forgery (CSRF) vulnerability in the MPG WordPress plugin, affecting versions <= 3.3.17. It carries a CVSS score of 3.1 (reachable over the network). Exploitation requires no authentication. The issue is fixed in version 3.3.18; sites on affected versions should update now. Disclosed May 2023, reported by Marco Wotschka.
Vulnerability Overview
The Multiple Page Generator Plugin for WordPress is vulnerable to Cross-Site Request Forgery leading to time-based SQL Injection via the orderby and order parameters in versions up to, and including, 3.3.17 due to missing nonce verification on the projects_list function and insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries leading to resource exhaustion via a forged request granted they can trick an administrator into performing an action such as clicking on a link. Version 3.3.18 addresses the SQL Injection, which drastically reduced the severity.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in MPG <= 3.3.17 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For MPG the fix is 3.3.18: builds <= 3.3.17 are affected, anything from 3.3.18 onward is not.
Remediation
Update to version 3.3.18, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to MPG: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: MPG 3.3.18 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
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 - 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-2026-85198: MPG <= 4.2.1 SQL Injection
CVE-2026-85198 - 6.5CVE-2024-47325: Multiple Page Generator Plugin – MPG SQL Injection
CVE-2024-47325 - 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
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C