dbcve.org
Post Grid MasterWordPress extension · Addonmaster

CVE-2025-24733

MEDIUM · 6.5 CVSS v3.1 Published 2025-01-24
Fix available
A fix is available. Upgrade to 3.4.13 or later.
See remediation →
71/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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Akhtarujjaman Shuvo Post Grid Master ajax-filter-posts allows PHP Local File Inclusion.This issue affects Post Grid Master: from n/a through <= 3.4.12.

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

A PHP Local File Inclusion vulnerability exists in the Post Grid Master plugin's ajax-filter-posts functionality. The vulnerability allows attackers to include local PHP files through improper validation of file path parameters, potentially leading to arbitrary code execution or sensitive file disclosure.

MitigationUpgrade to Post Grid Master version 3.4.13 or later. If unavailable, disable the ajax-filter-posts functionality or implement server-side input validation to restrict file paths to allowed directories.

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

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 version
    Check the installed version in WordPress under Plugins > Installed Plugins > Post Grid Master, or read the main plugin file (post-grid-master.php) and look for the 'Version' header comment
    Affected if The installed version is lower than 3.4.13 (e.g., 3.4.12, 3.4.10, etc.) or the version cannot be determined
  2. Locate the ajax-filter-posts endpoint
    Search for the ajax-filter-posts action in plugin PHP files (typically in includes/ajax.php or similar), or test accessing /wp-admin/admin-ajax.php?action=ajax-filter-posts
    Affected if The endpoint exists and responds, indicating the vulnerable functionality is active
  3. Inspect the file path parameter handling
    Open the PHP file containing the ajax-filter-posts handler and examine how file path parameters are processed (look for include, require, or similar functions using user-supplied input without validation)
    Affected if The code uses file path parameters from $_POST or $_GET in include/require statements without proper sanitization or path restriction

You are affected if Post Grid Master version is below 3.4.13 AND the ajax-filter-posts functionality is enabled, as the vulnerability requires both conditions to be exploitable.

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.13 or later
Fixed in 3.4.13
Interim mitigation

Upgrade to Post Grid Master version 3.4.13 or later. If unavailable, disable the ajax-filter-posts functionality or implement server-side input validation to restrict file paths to allowed directories.

Recommended fix High confidence

Post Grid Master version 3.4.13

  1. 1. Create a complete backup of your WordPress site (database and files) before updating.
  2. 2. Navigate to your WordPress admin dashboard > Plugins.
  3. 3. Find 'Post Grid Master' in your installed plugins list.
  4. 4. Click 'Update Now' to update the plugin to version 3.4.13.
  5. 5. Alternatively, you can update manually by downloading version 3.4.13 from the WordPress plugin repository and uploading it via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the plugin version shows 3.4.13 in the plugins list.
  7. 7. Test that the ajax-filter-posts functionality 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
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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