# CVE-2026-93747: wpForo Forum stored cross-site scripting in profile fields

Source: https://junglewise.ai/threats/cve-2026-93747-the-wpforo-forum-plugin-for-wordpress-is-vulnerable-to-stored  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-25. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-93747 · Severity: medium · CVSS 6.4 · Published 2026-09-25

wpForo Forum is a community forum plugin for WordPress that allows members to create user profiles. Authenticated attackers can inject malicious scripts into profile fields (specifically the telegram field) that execute when other users view the profile, potentially stealing session tokens, redirecting users, or performing unauthorized actions on their behalf.

Technologies: [wpForo Forum](https://junglewise.ai/threats/technologies/wpforo-wpforo-forum). Vendors: [wpForo](https://junglewise.ai/threats/vendors/wpforo).

## Quick answers

**Is CVE-2026-93747 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-93747 being exploited in the wild.

**How severe is CVE-2026-93747?** Medium severity, with a CVSS score of 6.4, published 25 September 2026.

**Which products and versions are affected?** wpForo Forum up to and including 3.1.6.

**Is there a fix for CVE-2026-93747?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-93747 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-93747?** Check whether you run wpForo Forum at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The plugin fails to sanitize user input from the $_POST['data'] array in the profile_update action before saving it to the database. The sanitize() and validate() functions operate on a separate $user variable rather than the $custom_fields array that gets persisted, leaving profile data unescaped. On page render, wpforo_decode() reverses HTML entity encoding and the value is echoed without escaping, enabling stored XSS. The vulnerability requires subscriber-level authentication or above.

## Affected products

- wpForo wpForo Forum up to and including 3.1.6

## Timeline

- 2026-09-25: disclosed

## References

- [https://plugins.trac.wordpress.org/browser/wpforo/tags/3.1.5/classes/Actions.php](https://plugins.trac.wordpress.org/browser/wpforo/tags/3.1.5/classes/Actions.php)
- [https://plugins.trac.wordpress.org/browser/wpforo/tags/3.1.5/classes/Forms.php](https://plugins.trac.wordpress.org/browser/wpforo/tags/3.1.5/classes/Forms.php)

## Related threats

- [WordPress wpForo Forum plugin SQL injection via data parameter](https://junglewise.ai/threats/cve-2026-95870-the-wpforo-forum-plugin-for-wordpress-is-vulnerable-to-generic)
- [wpForo Forum stored cross-site scripting in post body](https://junglewise.ai/threats/cve-2026-120532-the-wpforo-forum-plugin-for-wordpress-is-vulnerable-to-stored)
- [WordPress wpForo Forum plugin privilege escalation in secondary_groupids](https://junglewise.ai/threats/cve-2026-119164-the-wpforo-forum-plugin-for-wordpress-is-vulnerable-to-privilege)
- [wpForo Forum SQL injection in href locale parameter](https://junglewise.ai/threats/cve-2026-119155-the-wpforo-forum-plugin-for-wordpress-is-vulnerable-to-time)
- [wpForo Forum arbitrary file deletion in theme_delete](https://junglewise.ai/threats/cve-2026-110004-the-wpforo-forum-plugin-for-wordpress-is-vulnerable-to-arbitrary)