wpForo Forum <= 3.1.6 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'telegram' Profile Field
What fixes it
No source in this snapshot names a fixed version.
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.
Text from CVE List
Affected versions 1
- wpForo Forumaffected: all versions through 3.1.6CVE List
References 7
- wordfence.com/threat-intel/vulnerabilities/id/15dc1661-793a-43dd-8a12-8f51da6cb304?source=cveReferencevia CVE List
- plugins.trac.wordpress.org/browser/wpforo/tags/3.1.5/classes/Forms.php#L324Referencevia CVE List
- plugins.trac.wordpress.org/browser/wpforo/tags/3.1.5/classes/Forms.php#L1074Referencevia CVE List
- plugins.trac.wordpress.org/browser/wpforo/tags/3.1.5/classes/Members.php#L1157Referencevia CVE List
- plugins.trac.wordpress.org/browser/wpforo/tags/3.1.5/classes/Members.php#L906Referencevia CVE List
- plugins.trac.wordpress.org/browser/wpforo/tags/3.1.5/classes/Actions.php#L711Referencevia CVE List
- plugins.trac.wordpress.org/changeset?reponame=&old=3706608%40wpforo&new=3706608%40wpforoReferencevia CVE List