GiveWP donor PII disclosure in REST API endpoint
- Exploited
- No known exploitation
- Fix
- Fixed in 4.19.2.1
- Who is exposed
- Not reported
Summary
The GiveWP WordPress plugin does not properly restrict access to sensitive donor information in one of its REST API endpoints. Any logged-in user who owns a donor record, such as a subscriber who has donated once, can retrieve the email addresses, phone numbers, names, postal addresses and company details of all donors.
Written by a model
Original description
The GiveWP WordPress plugin before 4.19.2.1 does not properly restrict access to sensitive donor information in one of its REST API endpoints, allowing any authenticated user who owns a donor record, such as a subscriber who has donated once, to retrieve the email address, phone number, name, postal address and company of all donors.
What to do
Upgrade to a fixed version: 4.19.2.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-115226 (GiveWP < 4.19.2.1 - Subscriber+ Donor PII Disclosure via 'id' Parameter), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-115226 (entry last updated 2026-11-21):
Affected:
- Unknown GiveWP: fixed in 4.19.2.1
Fixed versions: 4.19.2.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-115226 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-115226 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- the references on https://cve.now/CVE-2026-115226
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-115226
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-115226"}.Affected versions
- Unknown GiveWPfixed in 4.19.2.1
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 55 if added to CISA KEV
- Would score about 50 if CISA's SSVC rates exploitation active
- Would score about 22 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-115226 |
| Record | NVD · CVE-2026-115226 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | wpscan.com · vulnerability/6fa0dbe3-5a2e-4219-8f66-7decbc569038 |
Questions about CVE-2026-115226
Is CVE-2026-115226 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-115226?
GiveWP: before 4.19.2.1.
Source: cve.now feed data
How do I fix CVE-2026-115226?
Upgrade to a fixed version: 4.19.2.1.
Source: cve.now feed data
Related
- CVE-2023-0224GiveWP < 2.24.1 - Unauthenticated SQLi
- CVE-2026-85530GiveWP < 4.16.8.1 - Unauthenticated Account Takeover via Donor Email Sanitization Mismatch
- CVE-2026-14319GiveWP < 4.16.3 - Unauthenticated Recurring Donor Information Disclosure
- CVE-2026-111979GiveWP < 4.19.0.1 - Give Worker+ Stored XSS via Form Template Primary Color
- CVE-2026-14318GiveWP < 4.16.3 - GiveWP Worker+ Stored XSS via Donation Form Template Settings
- CVE-2026-85113GiveWP < 4.16.9 - Unauthenticated Arbitrary Shortcode Execution via Donor Name
No corrections so far. Something wrong on this page? Report an error.