dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2024-7424

MEDIUM · 5.4 CVSS v3.1 Published 2024-11-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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
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.

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

The Multiple Page Generator Plugin – MPG for WordPress has a broken access control vulnerability where functions intended for administrator use lack proper capability checks. This allows any authenticated user with Subscriber-level access or higher to invoke admin functions, enabling unauthorized CSV file uploads and access to view MPG project contents.

MitigationUpdate to version 4.0.2 or later which implements proper capability checks on affected functions to restrict them to administrator-level users.

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

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
Low
Integrity
Low
Availability
None

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

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 MPG plugin is installed
    Inspect the WordPress plugins directory at /wp-content/plugins/ for a folder containing 'mpg' or 'multiple-page-generator' in the name, or use wp-cli: wp plugin list --status=active --format=csv
    Affected if The MPG plugin appears in the active plugins list
  2. Determine installed MPG plugin version
    Check the plugin header in the main MPG PHP file for the 'Version' field, or run: grep -i 'Version:' /path/to/wp-content/plugins/mpg/*.php | head -5, or use wp-cli: wp plugin get mpg --format=json
    Affected if The version is lower than 4.0.2 (e.g., 4.0.1, 4.0.0, or earlier)
  3. Verify MPG plugin is active on the site
    Confirm the plugin is actively running rather than just installed, using WordPress admin or wp-cli: wp plugin is-active mpg
    Affected if The plugin status shows as active
  4. Check for non-administrator user roles
    Query the WordPress database for users with roles other than administrator: SELECT user_id, meta_value FROM wp_usermeta WHERE meta_key = 'wp_capabilities' AND meta_value NOT LIKE '%administrator%'; (adjust wp_ prefix if different)
    Affected if There are users with Subscriber, Editor, Author, or Contributor roles present in the database
  5. Inspect plugin source for missing capability checks
    Examine the main MPG plugin PHP file for functions that handle CSV uploads or project viewing. Look for functions that lack current_user_can('manage_options') or similar admin-only checks, e.g., grep -n 'current_user_can' /path/to/mpg-plugin-file.php
    Affected if Admin functions such as file upload handlers or project access functions lack proper current_user_can() validation for administrator-level access

You are affected if MPG plugin version is below 4.0.2 AND the plugin is active AND your site has any authenticated users with Subscriber-level or higher access.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 4.0.2 or later which implements proper capability checks on affected functions to restrict them to administrator-level users.

Recommended fix Moderate confidence

Version 4.0.2 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'Multiple Page Generator Plugin – MPG' plugin
  4. Check if an update is available and update to the latest version (version 4.0.2 or higher)
  5. Alternatively, download the latest version from the WordPress plugin repository and reinstall

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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