# CVE-2023-2608: Multiple Page Generator Plugin <= 3.3.17 - Cross-Site Request Forgery to SQL Injection

> Unauthenticated attackers can exploit CSRF to trigger SQL injection in the Multiple Page Generator Plugin, potentially causing resource exhaustion or data exposure.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 May 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-wg5f-8xwf-672g

## What is CVE-2023-2608?

CVE-2023-2608 is a low-severity SQL injection vulnerability in themeisle Multiple Page Generator Plugin – MPG, published on 17 May 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2023-2608?

It affects 1 product.


Products: Themeisle Multiple Page Generator.

## How do I fix CVE-2023-2608?

No fix has been published for CVE-2023-2608 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-2608 being exploited?

There is no known exploitation of CVE-2023-2608 in the wild and no public exploit code.

## Other vulnerabilities in themeisle Multiple Page Generator Plugin – MPG

- [CVE-2024-27951](https://insights.sbomify.com/CVE-2024-27951/): WordPress Multiple Page Generator Plugin <= 3.4.0 - Auth. Remote Code Execution (RCE) vulnerability (critical 9.1)
- [CVE-2024-47325](https://insights.sbomify.com/CVE-2024-47325/): WordPress Multiple Page Generator Plugin – MPG plugin <= 3.4.7 - SQL Injection vulnerability (high 8.5)
- [CVE-2023-33927](https://insights.sbomify.com/CVE-2023-33927/): WordPress Multiple Page Generator Plugin – MPG Plugin <= 3.3.19 is vulnerable to SQL Injection (high 7.6)
- [CVE-2023-2607](https://insights.sbomify.com/CVE-2023-2607/): Multiple Page Generator Plugin <= 3.3.17 - Authenticated (Administrator+) SQL Injection (high 7.2)
- [CVE-2024-10705](https://insights.sbomify.com/CVE-2024-10705/): Multiple Page Generator Plugin – MPG <= 4.0.5 - Authenticated (Editor+) Server-Side Request Forgery via fileUrl (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-2608 and fix it if it is affected.

What it is: CVE-2023-2608 is a low-severity SQL injection vulnerability in themeisle Multiple Page Generator Plugin – MPG, published on 17 May 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-2608 in the wild and no public exploit code.

Affected product: themeisle Multiple Page Generator Plugin – MPG. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-2608/ (Markdown: https://insights.sbomify.com/CVE-2023-2608/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-2608
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-2608
- OSV: https://osv.dev/vulnerability/CVE-2023-2608

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-2608/
Summaries are generated and may contain mistakes; the official description above is the record.