Quick answers
- Is CVE-2026-104672 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104672 being exploited in the wild.
- How severe is CVE-2026-104672?
- High severity, with a CVSS score of 7.1, published 6 October 2026.
- Which products and versions are affected?
- StellarWP GiveWP <= 4.17.0.
- Is there a fix for CVE-2026-104672?
- Yes: fixed in 4.18.0 or later. Until then: If unable to update immediately, enable Patchstack's mitigation rule to block attacks until the patch is applied, or restrict access to donation forms while an update is pending. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-104672 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-104672?
- Check whether you run StellarWP GiveWP 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: 4.18.0 or later
If unable to update immediately, enable Patchstack's mitigation rule to block attacks until the patch is applied, or restrict access to donation forms while an update is pending.
Technical details
Stored cross-site scripting (XSS) flaw in GiveWP <= 4.17.0 allows unauthenticated attackers to inject malicious scripts without authentication. The vulnerability requires user interaction such as clicking a malicious link or visiting a crafted page. Successful exploitation permits theft of visitor session tokens, donation data, or execution of arbitrary actions in the context of vulnerable users' browsers.
Affected products
- StellarWP GiveWP <= 4.17.0
Timeline
- 2026-10-05: disclosed
- 2026-09-24: reported: initial report to vendor