wpForo Forum script injection via stored XSS in plugin pages
Affects wpForo Forum plugin 3.2.4 and earlier, a WordPress forum plugin by Tomdever. Fixed in 3.2.5.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.2.5
- Who is exposed
- Specific setups only
Summary
The wpForo Forum plugin by Tomdever for WordPress contains a stored cross-site scripting flaw. An attacker can remotely, without logging in, store malicious script that runs in a user's browser, but only after the user takes some action on the affected page.
Written by a model
Original description
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Tomdever wpForo Forum wpforo allows Stored XSS.This issue affects wpForo Forum: from n/a through 3.2.4.
Who should check
Sites running the wpForo Forum WordPress plugin version 3.2.4 or earlier, including WordPress hosts and site owners.
“<= 3.2.4 Vulnerable version(s)”
What to do
Check whether your setup matches what the bug needs.
wpForo Forum plugin version 3.2.4 or earlierUpgrade to a fixed version: 3.2.5.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-128996 (WordPress wpForo Forum plugin <= 3.2.4 - Cross Site Scripting (XSS) vulnerability), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-128996 (entry last updated 2026-11-20):
Affected:
- Tomdever wpForo Forum: fixed in 3.2.5
Fixed versions: 3.2.5.
Conditions (all must be true for the bug to be hit):
- wpForo Forum plugin version 3.2.4 or earlier (source: https://patchstack.com/database/wordpress/plugin/wpforo/vulnerability/wordpress-wpforo-forum-plugin-3-2-4-cross-site-scripting-xss-vulnerability?_s_id=cve)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-128996 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128996 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/wpforo/vulnerability/wordpress-wpforo-forum-plugin-3-2-4-cross-site-scripting-xss-vulnerability?_s_id=cve
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-128996
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-128996"}.Affected versions
- wpforofixed in 3.2.5 · through 3.2.4
cve.now Index
- Exploitation0/40No signal
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-128996 |
| Record | NVD · CVE-2026-128996 |
| Other links 1 | |
| Link | patchstack.com · database/wordpress/plugin/wpforo/vulnerability/wordpress-wpforo-forum-plugin-3-2-4-cross-site-scripting-xss-vulnerability?_s_id=cve |
Questions about CVE-2026-128996
Is CVE-2026-128996 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
This is a cross-site scripting flaw, which means malicious scripts can be injected into the site. The advisory says these scripts can steal visitor data or hijack visitor accounts.
Source: patchstack.com
Which versions are affected by CVE-2026-128996?
wpforo: through 3.2.4 (fixed in 3.2.5).
Source: cve.now feed data
Am I affected, and how do I check?
wpForo Forum plugin versions 3.2.4 and earlier are affected. To check a site, look up the installed plugin version on the WordPress Plugins screen or in the plugin's files.
Source: patchstack.com
How do I fix CVE-2026-128996?
Upgrade to a fixed version: 3.2.5. The vendor's advisory also recommends 3.2.5 or later or later.
Source: cve.now feed data, patchstack.com
Related
- CVE-2026-49767WordPress wpForo Forum plugin <= 3.1.0 - Broken Authentication vulnerability
- CVE-2026-49769WordPress wpForo Forum plugin <= 3.1.0 - PHP Object Injection vulnerability
- CVE-2026-40798WordPress wpForo Forum plugin <= 3.0.4 - SQL Injection vulnerability
- CVE-2026-42682WordPress wpForo Forum plugin <= 3.0.6 - Broken Access Control vulnerability
- CVE-2026-3666wpForo Forum <= 2.4.16 - Authenticated (Subscriber+) Arbitrary File Deletion via Post Body
- CVE-2026-57636WordPress wpForo Forum plugin <= 3.0.9 - SQL Injection vulnerability
No corrections so far. Something wrong on this page? Report an error.