GiveWP: Public rendering exposes unpublished donation forms
GiveWP renders donation forms through a public front-end route without checking form status or caller capability. An unauthenticated visitor can retrieve content and settings from draft, pending, private and scheduled forms that WordPress would otherwise keep non-public. The route identifier, selector parameter and exact exposed setting fields are not disclosed in the export. Published affected versions: < 4.19.0.1.
- Component
- GiveWP
- Plugin slug
give- Affected
- < 4.19.0.1
- Safe version
4.19.0.1- Published
- Oct 25, 2026
- Weakness
- Not assigned
This CVE was published Oct 25, 2026 and is one of 69 known issues for this plugin.
Update, patch or deactivate.
Update GiveWP to 4.19.0.1 or later. Enforce form-publication status and caller authorization before rendering content or settings. Avoid exposing non-public settings in public responses and assess whether unpublished information was accessed.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The GiveWP WordPress plugin before 4.19.0.1 does not perform any status or capability check when rendering a donation form on a public front-end route, allowing unauthenticated visitors to view the content and settings of unpublished (draft, pending, private and scheduled) donation forms that WordPress core otherwise keeps non-public.