Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') (CWE-98)
The wpForo Forum plugin for WordPress is vulnerable to Local File Include, Server-Side Request Forgery, and PHAR Deserialization in versions up to, and including, 2.1.7. This vulnerability is due to the insecure use of file_get_contents without appropriate verification of the data being supplied to the function. It affects authenticated attackers with minimal permissions, such as subscribers.
This vulnerability allows authenticated attackers with minimal permissions to retrieve the contents of sensitive files like wp-config.php hosted on the system, perform deserialization attacks potentially leading to remote code execution, and make requests to internal services. The impact on confidentiality, integrity, and availability is rated as HIGH, with a CVSS v3.1 base score of 8.8.
One proof-of-concept exploit is available on github.com. There is no evidence of proof of exploitation at the moment.
A patch is available. The vulnerability affects wpForo Forum plugin versions up to and including 2.1.7. Users should update to a version newer than 2.1.7 to mitigate this vulnerability.
1. Update the wpForo Forum plugin to a version newer than 2.1.7 immediately. 2. If immediate updating is not possible, consider temporarily disabling the plugin until it can be updated. 3. Implement strong authentication measures and regularly audit user permissions to minimize the risk of exploitation by authenticated users with low-level permissions. 4. Monitor for any suspicious activities or unauthorized file access attempts, especially those targeting sensitive files like wp-config.php. 5. Implement network segmentation to limit the potential impact of Server-Side Request Forgery attacks on internal services.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Feedly found the first article mentioning CVE-2023-2249. See article
CVE-2023-2249 is a critical vulnerability in the Wordpress Wpforo Plugin that allows remote attackers to reach internal endpoints and deploy malicious files. A proof-of-concept exploit is available on GitHub, increasing the likelihood of exploitation in the wild. Mitigations, detections, and patches are not yet available, posing a significant risk to users and potentially impacting third-party vendors who rely on the affected plugin. See article