HomeWordPress vulnerabilitiesMPG
MPG vulnerabilities
MPG has 9 known vulnerabilities in this database. The most recent published record is dated 7 Oct 2026.
- Known vulnerabilities
- 9
- Active installs
- 2,000+
- Latest version
- 4.2.4
- Last updated
- 28 Sep 2026
- Most recent
- 7 Oct 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| SQL injection CVE-2026-104953 | Medium 6.8 | Before 4.2.3 | Fixed in 4.2.3 | 18 h ago |
| Arbitrary file read CVE-2026-103293 | Medium 6.8 | Before 4.2.3 | Fixed in 4.2.3 | 4 d ago |
| SQL injection CVE-2026-85198 | Medium 6.5 | Up to 4.2.1 | Fixed in a later version (latest 4.2.4) | 12 Sep 2026 |
| Cross-site scripting (XSS) CVE-2026-13726 | High 7.1 | Before 4.1.8 | Fixed in 4.1.8 | 27 Jul 2026 |
| Server-side request forgery (SSRF) CVE-2024-10705 | Medium 5.4 | Before 4.0.6 | Fixed in 4.0.6 | 26 Jan 2025 |
| Arbitrary file deletion CVE-2024-10672 | Low 2.7 | Before 4.0.3 | Fixed in 4.0.3 | 12 Nov 2024 |
| Broken access control CVE-2024-7424 | Medium 5.4 | Up to 4.0.1 | Fixed in a later version (latest 4.2.4) | 1 Nov 2024 |
| SQL injection CVE-2023-2607 | High 7.2 | Up to 3.3.17 | Fixed in a later version (latest 4.2.4) | 9 Jun 2023 |
| SQL injection CVE-2023-2608 | Low 3.1 | Before 3.3.18 | Fixed in 3.3.18 | 17 May 2023 |
Read the published descriptions
- CVE-2026-104953, 7 Oct 2026
- The MPG WordPress plugin before 4.2.3 does not properly validate the structure of imported project data before using it in a database query, allowing users with the Editor role or higher to perform SQL injection attacks and read sensitive data such as password hashes. CVE record
- CVE-2026-103293, 3 Oct 2026
- The MPG WordPress plugin before 4.2.3 does not validate that the dataset source supplied when importing a project is a remote URL before treating it as a local filesystem path and copying that file into a publicly accessible uploads folder. This makes it possible for users with the Editor role and above to read the contents of arbitrary files on the server, with the copied file then retrievable by unauthenticated visitors. CVE record
- CVE-2026-85198, 12 Sep 2026
- 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. CVE record
- CVE-2026-13726, 27 Jul 2026
- The MPG WordPress plugin before 4.1.8 does not sanitise and escape a parameter before reflecting it back in the response, allowing unauthenticated attackers to perform Reflected Cross-Site Scripting against a victim who is induced to send a crafted request. CVE record
- CVE-2024-10705, 26 Jan 2025
- The Multiple Page Generator Plugin - MPG plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 4.0.5 via the 'mpg_download_file_by_link' function. This makes it possible for authenticated attackers, with editor-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services. CVE record
- CVE-2024-10672, 12 Nov 2024
- The Multiple Page Generator Plugin - MPG plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the mpg_upsert_project_source_block() function in all versions up to, and including, 4.0.2. This makes it possible for authenticated attackers, with editor-level access and above, to delete limited files on the server. CVE record
- CVE-2024-7424, 1 Nov 2024
- The Multiple Page Generator Plugin - MPG plugin for WordPress is vulnerable to unauthorized modification of and access to data due to a missing capability check on several functions in all versions up to, and including, 4.0.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to invoke those functions intended for admin use resulting in subscribers being able to upload csv files and view the contents of MPG projects. CVE record
- CVE-2023-2607, 9 Jun 2023
- The Multiple Page Generator Plugin for WordPress is vulnerable to time-based SQL Injection via the orderby and order parameters in versions up to, and including, 3.3.17 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 administrator privileges to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. CVE record
- CVE-2023-2608, 17 May 2023
- 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. CVE record
What to do if you run MPG
If you run MPG, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new MPG vulnerabilities
Free. We email you when a new vulnerability is published for MPG, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.