Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify site running GiveWP <= 4.19.0.1
-
ExploitSend request to unprotected plugin endpoint
-
ExecutionBypass missing authorization check
-
ImpactRead or modify restricted data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Affects GiveWP WordPress donation plugin versions <= 4.19.0.1. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N) this is remote and unauthenticated against a default installation with no user interaction, so the primary precondition is simply that a reachable site runs a vulnerable GiveWP version. The specific endpoint, parameter, or plugin feature whose authorization check is missing is NOT described in the available sources, so the exact trigger cannot be stated with confidence. Limiting factors on real-world impact: the flaw yields only low confidentiality and low integrity impact (C:L/I:L, no availability effect), so an attacker gains access to or modification of a bounded subset of plugin data rather than full site takeover. |
| Impact | This is a moderate-priority issue rather than a top-tier emergency. The CVSS 6.5 (medium) vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N is highly favorable to attackers on the access side - fully remote (AV:N), low complexity (AC:L), no privileges (PR:N) and no user interaction (UI:N) - meaning any unauthenticated remote attacker can reach the flaw against a default install. What holds the score down is impact: only low confidentiality and low integrity (C:L/I:L) with no availability effect, consistent with a CWE-862 missing-authorization flaw exposing or allowing modification of a bounded set of plugin data rather than full compromise. The vuln.today decision label is 'this_month', not 'act_now' or 'emergency', which aligns with the medium severity. Key corroborating signals are ABSENT from the input: no EPSS exploitation-probability score is provided, the CVE is NOT listed in CISA KEV, and no SSVC breakdown is supplied - so exploitation likelihood cannot be quantified from the data given. The only reference is the Patchstack advisory database entry, which is a vendor/coordinator advisory, not working exploit code. Net: a genuinely remote-unauthenticated but limited-impact access-control bug on a popular WordPress plugin - worth patching in the normal monthly cycle, not a drop-everything event. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker sends a crafted request directly to a GiveWP plugin endpoint on a vulnerable WordPress site (<= 4.19.0.1) that fails to enforce an authorization check, allowing them to read or alter data they should not have access to. No credentials, user interaction, or special timing are required. No public exploit code is identified in the provided data; the single reference is the Patchstack advisory, not a verified working exploit. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 30, 2026
Unauthenticated broken access control in the GiveWP WordPress donation plugin through version 4.19.0.1 lets remote attackers reach plugin operations that should require authorization, yielding limited confidentiality and integrity impact with no availability effect (CVSS 6.5). The assessed vector is AV:N/AC:L/PR:N/UI:N, so no credentials and no user interaction are needed, although the specific endpoint or parameter that lacks its capability check is not disclosed in the available sources. No CISA KEV entry and no public exploit code were identified at time of analysis, and the issue is scoped in the this_month (routine monthly patching) priority band rather than as an emergency.
RemediationAI
Update the GiveWP plugin to a release later than 4.19.0.1; the supplied data does not state an exact fixed version, so confirm the current patched release against the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/give/vulnerability/wordpress-givewp-plugin-4-19-0-1-broken-access-control-vulnerability?_s_id=cve) before upgrading, since no vendor-released patch version is identified at time of analysis. If the site cannot be updated immediately, deactivating or removing GiveWP closes the exposure entirely at the cost of taking donation forms and fundraising shortcodes offline; fronting the site with WAF or reverse-proxy rules that block unauthenticated requests to the affected plugin routes is an alternative once the advisory or plugin diff identifies them, with the trade-off that a rule overlapping public donation submission paths can block legitimate donations. Because the missing authorization is reachable without credentials, restricting wp-admin access or adding authentication to the WordPress backend does not mitigate it, and no public exploit code was identified that would justify emergency outage.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
GiveWP is an open-source donation and fundraising plugin for WordPress, maintained by Nexcess (StellarWP) and deployed on nonprofit and fundraising sites where the donation form is typically public by design. The root cause class is CWE-862 Missing Authorization: some plugin operation reachable over HTTP is not gated by a capability or authorization check, so a caller with no WordPress privileges can invoke functionality intended for a more privileged user. The reporting advisory does not identify the specific route, AJAX action, form handler, or parameter involved, so the trigger is not described in the available sources and the precise set of donation records, settings, or fields an attacker can read or alter remains unconfirmed. The CVSS impact metrics (C:L/I:L/A:N) bound the outcome to a limited subset of plugin data rather than site-wide compromise or full administrative takeover, and the rating is driven by the unauthenticated, no-interaction network path rather than by breadth of impact.
Know when Givewp gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Remote unauthenticated reachability with no interaction (AV:N/AC:L/PR:N/UI:N) per the broken-access-control description; impact bounded to limited data exposure/modification (C:L/I:L, A:N).
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Broken Access Control in GiveWP <= 4.19.0.1 versions.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all
The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all
Unauthenticated PHP object injection in the GiveWP WordPress donation plugin (all versions through 4.16.7.1) lets remote
Improper privilege management in the GiveWP WordPress donation plugin (affected ranging from 4.16.6 up to but not includ
GiveWP WordPress plugin before 4.16.3 exposes sensitive donor privacy data through an unauthenticated REST API endpoint
Stored cross-site scripting in the GiveWP WordPress plugin before version 4.16.3 allows authenticated users holding the
Stored cross-site scripting in GiveWP donation forms before 4.19.0.1 lets a user who already holds a custom GiveWP role
The Donations Widget plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.
The GiveWP WordPress plugin before 2.21.3 does not have CSRF in place when exporting data, and does not validate the exp
The GiveWP WordPress plugin before 2.17.3 does not escape the json parameter before outputting it back in an attribute i
The GiveWP - Donation Plugin and Fundraising Platform WordPress plugin before 2.10.0 was affected by a reflected Cross-S
The "Donation Plugin and Fundraising Platform" plugin before 2.3.1 for WordPress has wp-admin/edit.php csv XSS. Rated me
EUVD-2026-114310
GHSA-5xg3-xvhc-jc3h
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB