dbcve.org
Post Grid MasterWordPress extension · Addonmaster

CVE-2024-34390

MEDIUM · 6.5 CVSS v3.1 Published 2024-05-06
Fix available
A fix is available. Upgrade to 3.4.9 or later.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable

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 Input During Web Page Generation ('Cross-site Scripting') vulnerability in AddonMaster Post Grid Master allows Stored XSS.This issue affects Post Grid Master: from n/a through 3.4.8.

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

Stored Cross-site Scripting vulnerability in the Post Grid Master WordPress plugin allows authenticated or unauthenticated attackers to inject malicious JavaScript into plugin settings or post grid content. This payload executes when administrators or users view the affected pages, potentially leading to session hijacking or privilege escalation.

MitigationUpdate Post Grid Master to the latest version once available. If no patch exists, remove the plugin or implement output encoding and input validation at the application layer. Audit administrator accounts for compromise.

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.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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 for the 'post-grid-master' folder or look in wp-content/plugins/ for post-grid-master folder
    Affected if The plugin folder exists in the WordPress installation
  2. Identify installed version of Post Grid Master
    Open the main plugin file (post-grid-master.php) and locate the version number in the plugin header comment, or check via WordPress admin > Plugins > Post Grid Master
    Affected if Version number is less than 3.4.9 or cannot be determined (assumed vulnerable)
  3. Inspect plugin settings for injected scripts
    Navigate to Post Grid Master settings in WordPress admin. Examine all text fields, meta fields, and content areas where users can input data. View the page source to check for unexpected script tags or event handlers
    Affected if Malicious JavaScript code (script tags, javascript: URLs, or event handlers like onload/onerror) is present in any plugin settings or saved post grid content
  4. Check post grid content for suspicious entries
    Review any custom post types or post grid entries created by the plugin. Examine stored content in the wp_postmeta table for the plugin or check the post grid shortcode content for unsanitized input
    Affected if Stored XSS payloads are present in post grid content or metadata

A user is affected if Post Grid Master version is below 3.4.9 AND the plugin is active with accessible settings or post grid content that could accept user input.

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.9 or later
Fixed in 3.4.9
Interim mitigation

Update Post Grid Master to the latest version once available. If no patch exists, remove the plugin or implement output encoding and input validation at the application layer. Audit administrator accounts for compromise.

Recommended fix Moderate confidence

Post Grid Master version 3.4.9

  1. 1. Back up your WordPress site and database before making any changes.
  2. 2. Navigate to the WordPress admin dashboard.
  3. 3. Go to Plugins > Installed Plugins.
  4. 4. Find 'Post Grid Master' in the plugin list.
  5. 5. Check if the current version is below 3.4.9.
  6. 6. If an update is available, click 'Update Now' to upgrade to version 3.4.9.
  7. 7. Verify the update was successful by checking the plugin version.
  8. 8. Test the plugin functionality to ensure it works correctly after the upgrade.

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

Fix this in Post Grid Master 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-2024-34390 — 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-34390 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