CVE-2024-52386: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in RadiusTheme Classified Listing
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in RadiusTheme Classified Listing classified-listing allows PHP Local File Inclusion.This issue affects Classified Listing: from n/a through <= 3.1.16.
AI Analysis
Technical Summary
CVE-2024-52386 is a Local File Inclusion (LFI) vulnerability found in the RadiusTheme Classified Listing plugin for WordPress, specifically affecting versions up to 3.1.16. The vulnerability arises from improper control over the filename parameter used in PHP include or require statements, allowing an attacker to manipulate the input to include arbitrary files from the server's filesystem. This can lead to disclosure of sensitive files such as configuration files, password stores, or other critical data. In some scenarios, it may also enable remote code execution if the attacker can upload malicious files or leverage other chained vulnerabilities. The issue stems from insufficient validation or sanitization of user-supplied input that controls the file path in the PHP code. Although no public exploits are currently reported, the vulnerability is significant because LFI flaws are commonly exploited in web applications, especially those running PHP. The plugin is widely used in classified listing websites built on WordPress, making it a relevant target. The vulnerability does not have an assigned CVSS score yet, but its characteristics suggest a high severity. No patches or official fixes have been linked yet, so users must monitor vendor announcements closely. The vulnerability was published on November 16, 2024, and was reserved on November 11, 2024, indicating recent discovery and disclosure.
Potential Impact
The exploitation of this vulnerability can have severe consequences for affected organizations. Attackers can read sensitive files on the server, such as configuration files containing database credentials, API keys, or other secrets, leading to data breaches. In some cases, attackers may escalate the attack to execute arbitrary code on the server, resulting in full system compromise. This can lead to website defacement, data theft, or use of the compromised server as a pivot point for further attacks within the network. The availability of the website may also be impacted if attackers disrupt normal operations or delete critical files. Organizations relying on the Classified Listing plugin for their online classified platforms risk reputational damage, loss of customer trust, and potential regulatory penalties if sensitive user data is exposed. The lack of authentication requirements in some configurations increases the risk, as attackers can exploit the vulnerability remotely without credentials. The widespread use of WordPress and PHP in many countries means that the scope of affected systems is broad, potentially impacting small to large enterprises running classified listing websites.
Mitigation Recommendations
Until an official patch is released by RadiusTheme, organizations should implement the following mitigations: 1) Restrict access to the vulnerable plugin files and directories using web server configuration (e.g., .htaccess rules) to prevent unauthorized access to include parameters. 2) Employ Web Application Firewalls (WAFs) with rules designed to detect and block attempts to exploit LFI vulnerabilities, such as suspicious include path manipulations. 3) Disable or restrict PHP functions that allow file inclusion if not required, such as include(), require(), include_once(), and require_once(), or use PHP configuration directives to limit file access (open_basedir). 4) Monitor web server logs for unusual requests that attempt to manipulate file inclusion parameters. 5) Conduct a thorough audit of the plugin's usage and remove or replace it if possible with a more secure alternative. 6) Keep all WordPress core, themes, and plugins updated to the latest versions once patches become available. 7) Implement principle of least privilege on the server to limit the impact of any successful exploitation. 8) Educate developers and administrators about secure coding practices to avoid similar vulnerabilities in custom code.
Affected Countries
United States, India, Brazil, Germany, United Kingdom, Canada, Australia, France, Italy, Spain
CVE-2024-52386: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in RadiusTheme Classified Listing
Description
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in RadiusTheme Classified Listing classified-listing allows PHP Local File Inclusion.This issue affects Classified Listing: from n/a through <= 3.1.16.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2024-52386 is a Local File Inclusion (LFI) vulnerability found in the RadiusTheme Classified Listing plugin for WordPress, specifically affecting versions up to 3.1.16. The vulnerability arises from improper control over the filename parameter used in PHP include or require statements, allowing an attacker to manipulate the input to include arbitrary files from the server's filesystem. This can lead to disclosure of sensitive files such as configuration files, password stores, or other critical data. In some scenarios, it may also enable remote code execution if the attacker can upload malicious files or leverage other chained vulnerabilities. The issue stems from insufficient validation or sanitization of user-supplied input that controls the file path in the PHP code. Although no public exploits are currently reported, the vulnerability is significant because LFI flaws are commonly exploited in web applications, especially those running PHP. The plugin is widely used in classified listing websites built on WordPress, making it a relevant target. The vulnerability does not have an assigned CVSS score yet, but its characteristics suggest a high severity. No patches or official fixes have been linked yet, so users must monitor vendor announcements closely. The vulnerability was published on November 16, 2024, and was reserved on November 11, 2024, indicating recent discovery and disclosure.
Potential Impact
The exploitation of this vulnerability can have severe consequences for affected organizations. Attackers can read sensitive files on the server, such as configuration files containing database credentials, API keys, or other secrets, leading to data breaches. In some cases, attackers may escalate the attack to execute arbitrary code on the server, resulting in full system compromise. This can lead to website defacement, data theft, or use of the compromised server as a pivot point for further attacks within the network. The availability of the website may also be impacted if attackers disrupt normal operations or delete critical files. Organizations relying on the Classified Listing plugin for their online classified platforms risk reputational damage, loss of customer trust, and potential regulatory penalties if sensitive user data is exposed. The lack of authentication requirements in some configurations increases the risk, as attackers can exploit the vulnerability remotely without credentials. The widespread use of WordPress and PHP in many countries means that the scope of affected systems is broad, potentially impacting small to large enterprises running classified listing websites.
Mitigation Recommendations
Until an official patch is released by RadiusTheme, organizations should implement the following mitigations: 1) Restrict access to the vulnerable plugin files and directories using web server configuration (e.g., .htaccess rules) to prevent unauthorized access to include parameters. 2) Employ Web Application Firewalls (WAFs) with rules designed to detect and block attempts to exploit LFI vulnerabilities, such as suspicious include path manipulations. 3) Disable or restrict PHP functions that allow file inclusion if not required, such as include(), require(), include_once(), and require_once(), or use PHP configuration directives to limit file access (open_basedir). 4) Monitor web server logs for unusual requests that attempt to manipulate file inclusion parameters. 5) Conduct a thorough audit of the plugin's usage and remove or replace it if possible with a more secure alternative. 6) Keep all WordPress core, themes, and plugins updated to the latest versions once patches become available. 7) Implement principle of least privilege on the server to limit the impact of any successful exploitation. 8) Educate developers and administrators about secure coding practices to avoid similar vulnerabilities in custom code.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Patchstack
- Date Reserved
- 2024-11-11T06:38:47.503Z
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 69cd7540e6bfc5ba1df03996
Added to database: 4/1/2026, 7:42:56 PM
Last enriched: 4/2/2026, 8:57:51 AM
Last updated: 4/6/2026, 9:50:06 AM
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
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
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.