wpForo Forum <= 2.4.1 - Authenticated (Subscriber+) Arbitrary File Read in update
Strategic Overview
- Status
- Patched in 2.4.2
- Affected Plugin
- wpForo Forum
- Affected Version
<= 2.4.1- CVSS
- 6.5Medium
- Weakness type
- CWE-20 · Improper Input Validation
- CVE
CVE-2025-0764
At a glance
CVE-2025-0764 is a medium-severity Improper Input Validation vulnerability in the wpForo Forum WordPress plugin, affecting versions <= 2.4.1. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.4.2; sites on affected versions should update now. Disclosed February 2025, reported by mikemyers.
Vulnerability Overview
The wpForo Forum plugin for WordPress is vulnerable to arbitrary file read due to insufficient input validation in the 'update' method of the 'Members' class in all versions up to, and including, 2.4.1. This makes it possible for authenticated attackers, with subscriber-level privileges or higher, to read arbitrary files on the server.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality.
CWE-20: Improper Input Validation
wpForo Forum <= 2.4.1 carries this weakness at update, and reaching it takes an account at Subscriber level or above. Improper input validation means the application accepts input without confirming it has the form, type or range the code downstream assumes.
The concrete impact depends on where the unvalidated value lands, which is why records in this class range from cosmetic bugs to full compromise. For wpForo Forum the fix is 2.4.2: builds <= 2.4.1 are affected, anything from 2.4.2 onward is not.
Remediation
Update to version 2.4.2, or a newer patched version
How does WordSec protect against this?
An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: wpForo Forum 2.4.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in wpForo Forum
- 9.9CVE-2024-3200: wpForo Forum <= 2.3.3 SQL Injection
CVE-2024-3200 - 9.8CVE-2023-47868: wpForo Forum <= 2.2.3 Privilege Escalation
CVE-2023-47868 - 9.8CVE-2018-16613: wpForo < = 1.5.1 Privilege Escalation
CVE-2018-16613 - 9.8CVE-2018-11515: wpForo Forum <= 1.4.12 SQL Injection
CVE-2018-11515 - 8.8CVE-2026-3666: wpForo Forum <= 2.4.16 Arbitrary File Deletion
CVE-2026-3666 - 8.8CVE-2026-0910: wpForo Forum <= 2.4.13 PHP Object Injection
CVE-2026-0910 - 8.8CVE-2025-31420: wpForo Forum <= 2.4.3 Privilege Escalation
CVE-2025-31420 - 8.8CVE-2023-2249: wpForo Forum Local File Include, SSRF, and PHAR
CVE-2023-2249
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C