CVE-2025-30814
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in RadiusTheme The Post Grid the-post-grid allows PHP Local File Inclusion.This issue affects The Post Grid: from n/a through <= 7.7.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 confidenceA Local File Inclusion (LFI) vulnerability in the RadiusTheme The Post Grid WordPress plugin (versions up to 7.7.17) allows attackers to include arbitrary PHP files from the local server via improper input validation in include/require statements. This can lead to code execution if attackers can manipulate file paths to include malicious files.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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.
-
Verify The Post Grid plugin is installedLog into WordPress admin dashboard, navigate to Plugins > Installed Plugins, and search for 'The Post Grid' by RadiusTheme. Alternatively, check the /wp-content/plugins/ directory for the 'the-post-grid' folder.Affected if The Post Grid plugin by RadiusTheme is found installed on the WordPress site.
-
Determine installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins, find The Post Grid, and note the version number displayed under the plugin name. Alternatively, check the main plugin file (e.g., the-post-grid.php) in /wp-content/plugins/the-post-grid/ for the 'Version' header comment.Affected if The installed version is 7.7.17 or any earlier version (e.g., 7.7.16, 7.7.0, 6.0, etc.).
-
Identify exposed include/require pathsReview plugin source code in /wp-content/plugins/the-post-grid/ for PHP files containing include(), require(), include_once(), or require_once() statements that use variables or request parameters without proper sanitization (e.g., include($file), include($_GET['path']).Affected if Plugin code contains dynamic file inclusion using unsanitized input from $_GET, $_POST, or other user-controlled sources.
-
Check for accessible vulnerable endpointsTest common parameter names used in LFI (such as 'file', 'path', 'template', 'load', 'include') by requesting URLs like /?page=the-post-grid&file=../../../../wp-config.php (with appropriate encoding). Check if the plugin's shortcode or AJAX handlers accept and process file path parameters.Affected if The plugin accepts file path parameters that can be manipulated to include arbitrary local PHP files.
A user is affected if The Post Grid plugin version 7.7.17 or earlier is installed and the plugin exposes dynamic file inclusion functionality accessible to attackers.
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.
From vendor dataUpdate The Post Grid plugin to the latest patched version once released by RadiusTheme, or remove/replace the plugin if no patch is available. Review server PHP configuration to restrict file inclusion paths.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30814 — 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-30814 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