wpForo profile fields let Subscribers store JavaScript for administrators
wpForo Forum before 3.1.2 places a user profile field into an HTML attribute on the public participant profile page without sufficient sanitization and escaping. A Subscriber-level user can store a crafted value that breaks the attribute context and executes JavaScript for any visitor, including a logged-in Administrator, who views the profile. The record does not disclose the profile field, save action, output template or exact payload encoding.
- Component
- wpForo Forum
- Plugin slug
wpforo-forum- Affected
- < 3.1.2
- Safe version
3.1.2- Published
- Aug 01, 2026
- Weakness
- Not assigned
This CVE was published Aug 01, 2026 and is one of 9 known issues for this plugin.
Update, patch or deactivate.
Update wpForo Forum to 3.1.2 or later. Review profile values saved by Subscribers for attribute-breaking markup or scripts, remove confirmed payloads, and invalidate administrator sessions if a privileged user viewed an affected profile.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The wpForo Forum WordPress plugin before 3.1.2 does not sanitize and escape a user profile field before outputting it inside an HTML attribute on the public participant profile page, allowing users with a subscriber-level account to inject JavaScript that executes in the browser of any visitor who views the profile, including a logged-in administrator.