Quick answers
- Is CVE-2026-66617 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-66617 being exploited in the wild.
- How severe is CVE-2026-66617?
- Medium severity, with a CVSS score of 6.5, published 17 September 2026.
- Which products and versions are affected?
- PublishPress Series <= 3.1.3.
- Is there a fix for CVE-2026-66617?
- A patch was published on 2026-09-17: Fix available in version 3.1.4 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-66617 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-66617?
- Check whether you run PublishPress Series 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.
Technical details
This is a Contributor-level Stored Cross-Site Scripting (XSS) vulnerability in PublishPress Series versions 3.1.3 and earlier. The vulnerability exists due to improper input sanitization or output escaping in the plugin. Exploitation requires a user with Contributor privileges (or higher) to inject a malicious payload; however, successful attacks also depend on a victim (typically an administrator or editor) interacting with the compromised content, such as clicking a crafted link or visiting a malicious page. An attacker with contributor access can inject scripts that execute in the browsers of site visitors and administrators, leading to credential theft or account compromise. The vulnerability has been patched in version 3.1.4.
Affected products
- PublishPress Series <= 3.1.3
Timeline
- 2026-09-17: disclosed: Vulnerability published by Patchstack
- 2026-09-17: patched: Fix available in version 3.1.4