Quick answers
- Is CVE-2026-104405 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104405 being exploited in the wild.
- How severe is CVE-2026-104405?
- High severity, with a CVSS score of 8.1, published 6 October 2026.
- Which products and versions are affected?
- StellarWP GiveWP 4.17.0 and earlier.
- Is there a fix for CVE-2026-104405?
- Yes: fixed in 4.18.0. Until then: Update to version 4.18.0 or later immediately. If unable to update, request assistance from your hosting provider or web developer, and consider temporarily disabling the GiveWP plugin until patched.</anigation> </invoke> Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-104405 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-104405?
- 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
Update to version 4.18.0 or later immediately. If unable to update, request assistance from your hosting provider or web developer, and consider temporarily disabling the GiveWP plugin until patched.</anigation> </invoke>
Technical details
The vulnerability is a privilege escalation flaw requiring no authentication, classified as an identification and authentication failure. A low-privilege or anonymous user can exploit this to become an admin user with full site control. The flaw affects GiveWP versions 4.17.0 and earlier, with a fix available in version 4.18.0.
Affected products
- StellarWP GiveWP 4.17.0 and earlier
Timeline
- 2026-10-05: disclosed
- 2026-10-06: advisory