dbcve.org
Multiple Page GeneratorWordPress extension · Themeisle

CVE-2024-31301

HIGH · 8.8 CVSS v3.1 Published 2024-04-12
Fix available
A fix is available. Upgrade to 3.4.1 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross-Site Request Forgery (CSRF) vulnerability in Themeisle Multiple Page Generator Plugin – MPG.This issue affects Multiple Page Generator Plugin – MPG: from n/a through 3.4.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Themeisle Multiple Page Generator Plugin (MPG) allows attackers to execute unauthorized actions on behalf of authenticated users by tricking them into submitting malicious requests. The vulnerability exists in versions through 3.4.0, enabling attackers to potentially modify plugin settings, create or delete content, or perform other privileged actions if a user visits a malicious site while logged into the WordPress admin.

MitigationUsers should update to the latest version of MPG when patches are released. Site administrators can also implement additional CSRF protections at the web server level (e.g., SameSite cookie attributes) and ensure admin sessions are not vulnerable to session fixation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Multiple Page GeneratorWordPress extension
Affected:< 3.4.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Multiple Page Generator plugin is installed
    Locate the plugin directory 'multiple-page-generator' in wp-content/plugins/ or query the WordPress database: SELECT * FROM wp_options WHERE option_name = 'active_plugins';
    Affected if The plugin appears in active plugins list or plugin directory exists
  2. Identify the installed version of MPG
    Read the plugin header from wp-content/plugins/multiple-page-generator/mpg.php or check the WordPress plugins admin page for the installed version number
    Affected if Version displayed is below 3.4.1 (e.g., 3.4.0, 3.3.x, etc.)
  3. Verify the vulnerability is present
    This is a CSRF vulnerability - it affects any site where an administrator has an active session and visits a malicious external site. There is no config file or setting to check for this vulnerability itself; the presence of a vulnerable version is sufficient.
    Affected if Plugin version is below 3.4.1 AND administrators access the WordPress admin panel

A site is affected if the Themeisle Multiple Page Generator plugin version is below 3.4.1 and administrators have active sessions that could be exploited via CSRF.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.4.1 or later
Fixed in 3.4.1
Interim mitigation

Users should update to the latest version of MPG when patches are released. Site administrators can also implement additional CSRF protections at the web server level (e.g., SameSite cookie attributes) and ensure admin sessions are not vulnerable to session fixation.

Recommended fix High confidence

3.4.1

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in WordPress admin
  3. 3. Find 'Multiple Page Generator Plugin – MPG' (by Themeisle)
  4. 4. If an update is available, click 'Update Now' to upgrade to version 3.4.1
  5. 5. Alternatively, download version 3.4.1 from the WordPress plugin repository or Themeisle website
  6. 6. Deactivate and delete the current plugin version, then upload and install version 3.4.1
  7. 7. Verify the plugin is running version 3.4.1 after update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Multiple Page Generator Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-31301 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-31301 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data