dbcve.org
Multiple Page GeneratorWordPress extension · Themeisle

CVE-2022-47143

HIGH · 8.8 CVSS v3.1 Published 2023-03-14
Fix available
A fix is available. Upgrade to after 3.3.9 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 plugin <= 3.3.9 versions.

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 · high confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Themeisle Multiple Page Generator (MPG) plugin for WordPress versions 3.3.9 and below. The plugin fails to properly validate anti-CSRF tokens (nonces) on sensitive actions, allowing authenticated attackers to trick site administrators into unknowingly executing unwanted operations such as modifying plugin settings or creating/manipulating generated pages.

MitigationUpdate the MPG plugin to version 3.4.0 or later which implements proper nonce validation. If immediate update is not possible, ensure admin sessions are not left active on shared/public workstations and monitor for unexpected configuration changes.

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.3.9

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 MPG plugin version in WordPress admin
    Navigate to Plugins > Installed Plugins in the WordPress admin dashboard. Locate 'Multiple Page Generator (MPG)' and read the version number displayed under the plugin name.
    Affected if The version listed is 3.3.9 or any version number lower than 3.3.9 (for example, 3.3.8, 3.3.0, 2.0.0).
  2. Check plugin version via filesystem
    If you have file system access, open the main plugin file (typically /wp-content/plugins/multiple-page-generator/ or similar path containing 'mpg' or 'multiple-page-generator'). Look for the 'Version:' header in the plugin file header comment.
    Affected if The Version header shows 3.3.9 or below.
  3. Confirm plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify the MPG plugin has the 'Active' status under the plugin name.
    Affected if The plugin is active and the version is 3.3.9 or below. An inactive plugin with a vulnerable version is not exploitable.
  4. Check for admin users
    Navigate to Users > All Users in WordPress admin. Identify users with Administrator role.
    Affected if There are administrator-level users on the site. CSRF attacks target authenticated administrators, so the presence of admin users means the vulnerability could be triggered if they visit a malicious page while logged in.

You are affected if the MPG plugin is installed, active, and the version is 3.3.9 or lower - all such installations lack proper nonce validation and are vulnerable to CSRF attacks against administrators.

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 a release after 3.3.9
Interim mitigation

Update the MPG plugin to version 3.4.0 or later which implements proper nonce validation. If immediate update is not possible, ensure admin sessions are not left active on shared/public workstations and monitor for unexpected configuration changes.

Recommended fix Moderate confidence

Version 3.4.0 or later

  1. 1. Back up your WordPress site and database before making any changes.
  2. 2. Update the Multiple Page Generator (MPG) plugin to the latest available version from the WordPress plugin repository or Themeisle website.
  3. 3. Verify the update was successful by checking the plugin version in WordPress admin > Plugins.
  4. 4. Test critical functionality of the plugin to ensure the update did not break existing pages/templates.
Caveat Review plugin changelog for any template or configuration changes that may require adjustments

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
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-47143 — 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-2022-47143 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