Description
The wpForo Forum plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'telegram' profile field in versions up to, and including, 3.1.6. This is due to insufficient input sanitization and output escaping in the profile_update action — the raw $_POST['data'] array is copied into a $custom_fields variable before validate() and sanitize() run, both of which operate only on a parallel $user reference, leaving $custom_fields unsanitized when it is persisted via update_custom_fields(); on render, wpforo_decode() reverses the entity encoding and the value is echoed without escaping in field_wrap_profile(). This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
References7
- plugins.trac.wordpress.org/browser/wpforo/tags/3.1.5/classes/Ac…
- plugins.trac.wordpress.org/browser/wpforo/tags/3.1.5/classes/Fo…
- plugins.trac.wordpress.org/browser/wpforo/tags/3.1.5/classes/Fo…
- plugins.trac.wordpress.org/browser/wpforo/tags/3.1.5/classes/Me…
- plugins.trac.wordpress.org/browser/wpforo/tags/3.1.5/classes/Me…
- plugins.trac.wordpress.org/changeset?reponame=&old=3706608%40wp…
- www.wordfence.com/threat-intel/vulnerabilities/id/15dc1661-793a…
Metrics
- CVSS 3.1
-
6.4
MEDIUM
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N - EPSS — exploit probability
- 0% percentile: 9 · as of 9 November 2026
- CWE
- CWE-79
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.