dbcve.org
Post Grid MasterWordPress extension · Addonmaster

CVE-2024-34372

MEDIUM · 5.3 CVSS v3.1 Published 2024-05-06
Fix available
A fix is available. Upgrade to 3.4.8 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Missing Authorization vulnerability in AddonMaster Post Grid Master.This issue affects Post Grid Master: 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

Missing Authorization vulnerability in AddonMaster Post Grid Master plugin allows unauthenticated attackers to access certain functionality without proper capability checks. The CVSS 5.3 indicates low attack complexity with limited scope impact to confidentiality, integrity, or availability.

MitigationUpdate Post Grid Master to the latest version which should include proper authorization checks. If updates are unavailable, review and restrict access to affected plugin functions via server-side configuration or disable the plugin until a patch is released.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Verify Post Grid Master plugin is installed
    Check the WordPress plugins directory or access wp-admin > Plugins to see if 'Post Grid Master' or 'AddonMaster Post Grid Master' is listed among installed plugins.
    Affected if The plugin appears in the installed plugins list.
  2. Determine the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and look for the Post Grid Master entry. The version number is displayed below the plugin name. Alternatively, check the plugin's main PHP file header for the 'Version' tag.
    Affected if The displayed version number is less than 3.4.8.
  3. Check plugin files for vulnerable endpoints
    Inspect the plugin directory (wp-content/plugins/post-grid-master/) for PHP files containing AJAX action hooks or public function endpoints. Look for files with 'ajax' in the name or action hooks registered with 'wp_ajax_' or 'wp_ajax_nopriv_' prefixes.
    Affected if AJAX endpoints are registered that handle sensitive operations without capability checks.
  4. Test for unauthenticated access to plugin functions
    Send a direct HTTP request to common WordPress AJAX endpoints (admin-ajax.php) with action parameters related to Post Grid Master (e.g., action=pgm_some_function) without providing authentication cookies or nonce tokens.
    Affected if The plugin responds to unauthenticated requests and returns sensitive data or performs actions without rejecting the request.
  5. Review capability checks in plugin code
    Open the plugin's main PHP files and search for 'current_user_can', 'capability', or 'manage_options' function calls. Verify that these authorization checks are present before executing sensitive operations.
    Affected if Critical plugin functions lack capability checks or use weak/incorrect permission verification.

A user is affected if the Post Grid Master plugin version is below 3.4.8 and the plugin responds to unauthenticated requests for protected functionality.

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 Post Grid Master to the latest version which should include proper authorization checks. If updates are unavailable, review and restrict access to affected plugin functions via server-side configuration or disable the plugin until a patch is released.

Recommended fix Moderate confidence

Post Grid Master version 3.4.8

  1. 1. Back up your WordPress site and database before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in WordPress admin
  3. 3. Find 'Post Grid Master' in the plugin list
  4. 4. If update to version 3.4.8 is available, click 'Update Now'
  5. 5. If no update is shown, manually download version 3.4.8 from WordPress plugin repository or the vendor
  6. 6. Deactivate the current Post Grid Master plugin
  7. 7. Delete the current plugin files (or upload the new version via Plugins > Add New > Upload Plugin)
  8. 8. Reactivate the plugin after update

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

Fix this in Post Grid Master 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 the upgrade done

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-34372 — 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-34372 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