Quick answers
- Is CVE-2026-91829 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-91829 being exploited in the wild.
- How severe is CVE-2026-91829?
- High severity, with a CVSS score of 7.1, published 11 October 2026.
- Which products and versions are affected?
- WordPress Plugin Subscribe to Comments before 2.3.3.
- Is there a fix for CVE-2026-91829?
- Yes: fixed in 2.3.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-91829 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-91829?
- Check whether you run WordPress Plugin Subscribe to Comments at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.3.3
Technical details
The plugin fails to validate and sanitize the 'ref' parameter before reflecting it into a link target attribute, enabling reflected XSS. An unauthenticated attacker can craft a URL containing malicious JavaScript that executes when clicked by any user, including administrators. No authentication or user interaction beyond clicking a link is required from the attacker's perspective.
Affected products
- WordPress Plugin Subscribe to Comments before 2.3.3
Timeline
- 2026-10-09: disclosed