Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-30814: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in RadiusTheme The Post Grid

0
Unknown
VulnerabilityCVE-2025-30814cvecve-2025-30814
Published: Thu Mar 27 2025 (03/27/2025, 10:55:03 UTC)
Source: CVE Database V5
Vendor/Project: RadiusTheme
Product: The Post Grid

Description

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

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/02/2026, 00:21:46 UTC

Technical Analysis

CVE-2025-30814 is a Local File Inclusion (LFI) vulnerability found in the RadiusTheme WordPress plugin 'The Post Grid' in versions up to and including 7.7.17. The vulnerability arises from improper control over the filename parameter used in PHP include or require statements. This flaw allows an attacker to manipulate the filename input to include arbitrary files from the local server filesystem. Such an inclusion can lead to disclosure of sensitive files (e.g., configuration files, password files), or in some cases, execution of malicious code if the attacker can upload files to the server. The vulnerability is classified as a PHP Remote File Inclusion type but is specifically a Local File Inclusion due to the nature of the flaw. No CVSS score has been assigned yet, and no public exploits have been observed. The plugin is widely used in WordPress environments to display posts in grid layouts, making it a common target. The vulnerability requires the plugin to be installed and active, and exploitation typically involves sending crafted HTTP requests that manipulate the vulnerable parameter. The lack of proper input validation or sanitization in the plugin's code is the root cause. This vulnerability can lead to significant confidentiality and integrity breaches, including site defacement, data leakage, or further compromise through chained exploits.

Potential Impact

The impact of CVE-2025-30814 on organizations worldwide can be severe. Successful exploitation can lead to unauthorized disclosure of sensitive server files, including credentials, configuration files, or other critical data. Attackers may leverage this information to escalate privileges or gain deeper access to the hosting environment. In some scenarios, attackers might execute arbitrary code if they can upload malicious files, leading to full site compromise, defacement, or use of the server for malicious activities such as phishing or malware distribution. This can result in reputational damage, loss of customer trust, regulatory penalties, and operational disruption. Since WordPress powers a significant portion of the web, and The Post Grid plugin is popular among content-heavy sites, the scope of affected systems is large. The vulnerability particularly threatens organizations that rely on WordPress for their public-facing websites, including e-commerce, media, and service providers. The absence of known exploits currently provides a window for remediation, but the ease of exploitation and potential impact make this a critical risk to address promptly.

Mitigation Recommendations

To mitigate CVE-2025-30814, organizations should immediately update The Post Grid plugin to a patched version once available from RadiusTheme. Until a patch is released, administrators should consider disabling or uninstalling the plugin if it is not essential. Implementing Web Application Firewalls (WAFs) with rules to detect and block suspicious requests targeting include/require parameters can reduce exploitation risk. Restricting file system permissions to limit the web server's access to sensitive files can minimize damage from LFI attacks. Additionally, monitoring web server logs for unusual parameter values or access patterns related to the plugin can help detect exploitation attempts early. Developers should review and sanitize all user inputs used in file inclusion functions, employing whitelisting of allowed filenames and avoiding dynamic includes based on user input. Employing security plugins that detect and block LFI attempts on WordPress sites can provide an additional layer of defense. Regular backups and incident response plans should be in place to recover quickly if compromise occurs.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2025-03-26T09:20:32.696Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69cd731ee6bfc5ba1def083f

Added to database: 4/1/2026, 7:33:50 PM

Last enriched: 4/2/2026, 12:21:46 AM

Last updated: 4/6/2026, 11:30:45 AM

Views: 6

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses