Post Grid MasterWordPress extension · Addonmaster
CVE-2025-30974
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 · uneditedMissing Authorization vulnerability in Akhtarujjaman Shuvo Post Grid Master ajax-filter-posts allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Post Grid Master: from n/a through <= 3.4.17.
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 confidenceThe Post Grid Master WordPress plugin's ajax-filter-posts functionality lacks proper authorization checks, allowing unauthenticated or unauthorized users to access sensitive functionality that should be restricted. This missing authorization vulnerability in the AJAX endpoint enables attackers to exploit incorrectly configured access control security levels.
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
<= 3.4.13CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed plugin versionNavigate to WordPress admin > Plugins > Installed Plugins > Addonmaster Post Grid Master and note the version number displayedAffected if The installed version is 3.4.13 or lower (any version <= 3.4.13)
-
Locate the ajax-filter-posts AJAX handler fileInspect the plugin directory (wp-content/plugins/addonmaster-post-grid-master/) for files containing 'ajax-filter-posts' or examine the main plugin PHP file for registered AJAX actions using add_action('wp_ajax_ajax-filter-posts') or add_action('wp_ajax_nopriv_ajax-filter-posts')Affected if The AJAX endpoint 'ajax-filter-posts' is registered without capability checks (no current_user_capability or nonce validation before processing)
-
Verify authorization implementation in AJAX handlerSearch the plugin PHP files for the ajax-filter-posts callback function and examine if it contains current_user_can(), check_admin_referer(), or wp_verify_nonce() calls before executing sensitive operationsAffected if The callback function lacks capability verification (current_user_can) OR lacks nonce validation (check_admin_referer or wp_verify_nonce)
-
Check for nopriv AJAX registrationSearch for 'wp_ajax_nopriv_ajax-filter-posts' in plugin files - this indicates the endpoint is accessible to unauthenticated usersAffected if The plugin registers the ajax-filter-posts action with wp_ajax_nopriv_ (making it accessible to unauthenticated users) AND lacks proper authorization checks in the handler
Your environment is affected if the Post Grid Master plugin version is 3.4.13 or lower AND the ajax-filter-posts AJAX endpoint is accessible to unauthenticated users or lacks capability verification in its handler code.
Generated from the published advisory. Verify against your own configuration.
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 · scopedImplement proper authorization checks (capability verification) and nonce validation in the ajax-filter-posts AJAX handlers to ensure only authorized users can access the functionality.
Post Grid Master 3.4.18 or later
- Backup your WordPress site before making any changes
- Navigate to Plugins > Installed Plugins in WordPress admin
- Locate Post Grid Master in the plugin list
- Click Update Now to install the latest version, or manually download the updated plugin from wordpress.org
- Verify the plugin updated successfully to version 3.4.18 or later
- Test the ajax-filter-posts functionality to ensure it still works correctly after the update
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
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30974 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-30974 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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