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.
CVE-2026-93747
This medium-severity CVE scores 6.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.4
- EG Score
- 6.4(low)
- EG Risk
- 33(Track)EG Risk 33/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity64% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 25, 2026
Last Modified
September 25, 2026
References (7)
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wpforo/tags/3.1.5/classes/Actions.php#L711
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wpforo/tags/3.1.5/classes/Forms.php#L1074
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wpforo/tags/3.1.5/classes/Forms.php#L324
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wpforo/tags/3.1.5/classes/Members.php#L1157
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wpforo/tags/3.1.5/classes/Members.php#L906
- security@wordfencehttps://plugins.trac.wordpress.org/changeset?reponame=&old=3706608%40wpforo&new=3706608%40wpforo
- security@wordfencehttps://www.wordfence.com/threat-intel/vulnerabilities/id/15dc1661-793a-43dd-8a12-8f51da6cb304?source=cve
Vendor Advisories for CVE-2026-93747(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-25 08:27 UTCEG score recompute
- 2026-09-25 07:47 UTCEG score recompute
- 2026-09-25 07:46 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-93747?
When was CVE-2026-93747 disclosed?
What is the CVSS score of CVE-2026-93747?
How do I remediate CVE-2026-93747?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-93747
Is Your Infrastructure Affected by CVE-2026-93747?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.