dbcve.org
Multiple Page GeneratorWordPress extension · Themeisle

CVE-2024-47325

HIGH · 8.8 CVSS v3.1 Published 2024-10-20
Fix available
A fix is available. Upgrade to 3.4.8 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Themeisle MPG multiple-pages-generator-by-porthas allows SQL Injection.This issue affects MPG: from n/a through <= 3.4.7.

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

SQL Injection vulnerability in Themeisle MPG (multiple-pages-generator-by-porthas) WordPress plugin allows remote attackers to inject malicious SQL commands via unsanitized input, potentially enabling unauthorized data access or complete database compromise.

MitigationUpdate MPG plugin to the latest version beyond 3.4.7 immediately. As an interim control, deploy a WAF rule to detect and block SQL injection attack patterns until the patch is applied.

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

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Verify MPG plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Multiple Page Generator. The version number is displayed below the plugin name. Alternatively, check the plugin's main PHP file header or version.php file in the plugin directory.
    Affected if Installed version is lower than 3.4.8 (e.g., 3.4.7, 3.4.6, etc.)
  2. Confirm plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify the Multiple Page Generator status shows as 'Active'.
    Affected if Plugin is active and version is below 3.4.8
  3. Review WordPress debug logs for SQL errors
    Check wp-content/debug.log (if debug logging is enabled) for SQL syntax errors, warnings, or unusual database errors occurring around plugin functionality.
    Affected if SQL errors or suspicious database queries are present in logs connected to MPG functionality
  4. Audit database user privileges
    Check the WordPress database user in wp-config.php has been granted only necessary privileges. A successful SQL injection exploit may have created unexpected tables or modified existing ones.
    Affected if Database contains unexpected new tables, modified records, or the database user has elevated privileges beyond what MPG requires

A user is affected if the Multiple Page Generator plugin is active and the installed version is below 3.4.8, exposing the unsanitized input to potential SQL injection attacks.

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.8 or later
Fixed in 3.4.8
Interim mitigation

Update MPG plugin to the latest version beyond 3.4.7 immediately. As an interim control, deploy a WAF rule to detect and block SQL injection attack patterns until the patch is applied.

Recommended fix High confidence

Multiple Page Generator (MPG) version 3.4.8

  1. 1. Backup your WordPress site database and files before performing any updates
  2. 2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. 3. Find 'Multiple Page Generator' (MPG) plugin in the list
  4. 4. Click 'Update now' if an update is available, or manually update to version 3.4.8
  5. 5. Verify the plugin version shows 3.4.8 after updating
  6. 6. Test that the plugin functionality works as expected on your site

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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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