wpForo Forum <= 2.1.8 - Reflected Cross-Site Scripting via 'wpforo_debug'
Strategic Overview
- Status
- Patched in 2.1.9
- Affected Plugin
- wpForo Forum
- Affected Version
<= 2.1.8- CVSS
- 6.1Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2023-2309
At a glance
CVE-2023-2309 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the wpForo Forum WordPress plugin, affecting versions <= 2.1.8. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.1.9; sites on affected versions should update now. Disclosed July 2023, reported by Alex Sanford.
Vulnerability Overview
The wpForo Forum plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the ‘wpforo_debug’ function in versions up to, and including, 2.1.8 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.
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 privileges on the target site.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
wpForo Forum <= 2.1.8 carries this weakness at wpforo_debug, and reaching it takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For wpForo Forum the fix is 2.1.9: builds <= 2.1.8 are affected, anything from 2.1.9 onward is not.
Remediation
Update to version 2.1.9, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to wpForo Forum: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: wpForo Forum 2.1.9 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
- 6.4CVE-2026-12696: wpForo Forum <= 3.1.1 Stored Cross-Site Scripting
CVE-2026-12696 - 6.4CVE-2026-15021: wpForo Forum <= 3.1.1 Stored Cross-Site Scripting
CVE-2026-15021 - 6.4CVE-2023-47872: wpForo Forum <= 2.2.3 Stored Cross-Site Scripting
CVE-2023-47872 - 6.1CVE-2019-19111: wpForo Forum <= 1.6.5 Cross-Site Scripting
CVE-2019-19111
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