CVE-2023-2249
HighwpForo Forum <= 2.1.7 - Authenticated (Subscriber+) Local File Include, Server-Side Request Forgery, and PHAR Deserialization via file_get_contents
Published May 31, 2023 · Updated Apr 8, 2026 · Also known as 800fa098-b29f-4979-b7bd-b1186a4dafcb
Key Facts
Patch immediately- CVE-2023-2249 is a high-severity vulnerability (CVSS 8.8 v3.1) affecting wpForo Forum (Gvectors), wpforo (wordpress-plugin).
- It is not listed in any known-exploited vulnerabilities catalog. No public exploit code is known.
- EPSS estimates a 61% probability of exploitation in the next 30 days.
- Fixed versions are available, including wpForo Forum 2.1.7, wpforo 2.1.8.
- Brandefense priority: patch immediately, because it is very likely to be exploited soon.
CVSS v3.1
8.8
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (30-day exploit likelihood)
61%
Higher than 99.1% of all scored CVEs
Exploited in the wild
No known
Not in a known-exploited catalog
Public exploit code
None known
Get the full CVE-2023-2249 brief as a PDF
Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.
Description
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 is due to the insecure use of file_get_contents without appropriate verification of the data being supplied to the function. This makes it possible for authenticated attackers, with minimal permissions such as a subscriber, to retrieve the contents of files like wp-config.php hosted on the system, perform a deserialization attack and possibly achieve remote code execution, and make requests to internal services.
Affected Products
3 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| wpForo ForumGvectors | See advisory | 2.1.7 |
| wpforowordpress-plugin | See advisory | 2.1.8 |
Patched Releases
wpForo Forum
2.1.7
wpforo
2.1.8
Timeline
Publicly disclosed
May 31, 2023
Last updated
Apr 8, 2026
Weakness Type
- CWE-98 Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
- CWE-829 Inclusion of Functionality from Untrusted Control Sphere
- CWE-918 Server-Side Request Forgery (SSRF)
References
- advisoryhttps://www.wordfence.com/threat-intel/vulnerabilities/id/800fa098-b29f-4979-b7bd-b1186a4dafcb?source=api-prod
- advisoryhttps://www.wordfence.com/threat-intel/vulnerabilities/id/800fa098-b29f-4979-b7bd-b1186a4dafcb?source=api-scan
- advisoryhttps://www.wordfence.com/threat-intel/vulnerabilities/id/800fa098-b29f-4979-b7bd-b1186a4dafcb?source=cve
- patchhttps://plugins.trac.wordpress.org/browser/wpforo/tags/2.1.7/classes/Actions.php#L444
- patchhttps://plugins.trac.wordpress.org/browser/wpforo/tags/2.1.8/classes/Actions.php#L437
FAQ
Common Questions.
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.
Affected: wpForo Forum (Gvectors); wpforo (wordpress-plugin). The full list is in the CVE brief.
It is not listed in any known-exploited vulnerabilities catalog.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
No public exploit code is known.
Fixed versions are available, including wpForo Forum 2.1.7, wpforo 2.1.8.
Brandefense priority: patch immediately, because it is very likely to be exploited soon.
Is CVE-2023-2249 Running On Your Attack Surface?
Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.
Request A Demo