WordPress wpForo Forum plugin <= 3.1.5 - Cross Site Scripting (XSS) vulnerability

Why this deserves its current priority

CVSS is 6.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps Tomdever/wpForo Forum (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for Tomdever/wpForo Forum.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Sep 23, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 23, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 23, 2026

Sources and claim methodology

• Source referencepatchstack.com

Related CVEs

• OpenC3 COSMOS: Stored, cross-user XSS via Telemetry screen BUTTON widgetAlso CWE-79
• Automation-controller: automation-controller-container: automation-controller: stored cross-site scripting in the job stdout html view via ansi osc 8 hyperlink sequences (javascript: anchor) enabling session takeoverAlso CWE-79
• Jawn: Uncontrolled nesting depth in JSON parserSame generic ecosystem
• Wire Swift runtime: negative LENGTH_DELIMITED length in skipGroup() crashes any protobuf-decoding serviceSame generic ecosystem
• Jawn: Quadratic parsing effort in AsyncParserSame generic ecosystem
• Formie: Integration form-settings action allows SSRF and exfiltration of stored integration credentialsSame generic ecosystem