# wpForo Forum <= 3.2.4 - Authenticated (Subscriber+) Stored Cross-Site Scripting via Profile Fields

- **ID:** WPSEC-2026-3155
- **Plugin:** wpForo Forum (`wpforo`), https://wordpress.org/plugins/wpforo/
- **Affected versions:** all versions before 3.2.5
- **Fixed in:** 3.2.5 (Update to 3.2.5 or later.)
- **Severity:** Medium 6.4 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N)
- **Weakness:** CWE-79
- **Usage among sites WPSec scans:** plugin Medium, affected versions Medium (as of 2026-11-15)
- **Attack surface analysis:** https://attacksurface.wpsec.com/plugin/wpforo
- **Fix released:** 2026-11-14
- **Published:** 2026-11-15
- **URL:** https://wpsec.com/vuln/WPSEC-2026-3155/

## Description

The wpForo Forum plugin for WordPress is vulnerable to Stored Cross-Site Scripting via user profile fields (display name, first and last name, website URL, about/description and rich-text fields such as the signature) in all versions up to, and including, 3.2.4. This is due to insufficient input sanitization when these fields are saved during profile updates and registration, and missing output escaping where they are rendered, such as in quote blocks and the admin members list. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts that will execute whenever a user, including an administrator, accesses a page displaying the injected profile data.

## References

- https://wpsec.com/vuln/WPSEC-2026-3155/
- https://plugins.svn.wordpress.org/wpforo/tags/3.2.5/
- https://wordpress.org/plugins/wpforo/

Source: WPSec, https://wpsec.com/vuln/WPSEC-2026-3155/

License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Free to use, share and adapt, also commercially, if you credit WPSec and link to this advisory.