Security readout for executives and security teams
Plain-English summary
GiveWP versions through 4.16.7.1 contain a critical flaw that could let an unauthenticated remote attacker execute code on an affected WordPress server. Successful compromise could expose donor or site data, alter content, disrupt services, and provide control beyond the plugin because the CVSS scope is changed.
Executive priority
Treat as an emergency remediation item for internet-facing donation sites. Assign ownership immediately, inventory affected installations, apply confirmed vendor guidance, and investigate potentially exposed hosts. Business leaders should account for possible donor-data exposure, website manipulation, payment-related disruption, and recovery requirements, while avoiding claims of compromise without evidence.
Technical view
The vulnerability is CWE-502: unsafe deserialization of untrusted data leading to PHP object injection and potentially remote code execution. The supplied CVSS 3.1 vector is 10.0, network-accessible, low complexity, unauthenticated, requiring no user interaction, with high confidentiality, integrity, and availability impact. The cited affected range ends at 4.16.7.1.
Likely exposure
WordPress installations running the GiveWP plugin at version 4.16.7.1 or earlier are potentially exposed. The bundle lists the starting version as “n/a” and marks unspecified versions unaffected, so inventory confirmation is important. Internet-accessible sites are the highest priority because the supplied vector indicates remote, unauthenticated attackability.
Exploitation context
The supplied record is not in KEV, and no source in the bundle establishes active exploitation. This does not prove exploitation is absent. The unauthenticated, low-complexity network vector and potential code execution make rapid defensive action appropriate without assuming attacks are currently occurring.
Researcher notes
The bundle supports unsafe deserialization, object injection, potential RCE, affected versions through 4.16.7.1, and CVSS 10.0. It does not provide a confirmed fixed version, technical root-cause detail, attack indicators, or evidence of exploitation. Avoid inferring a specific patch version from the affected-range endpoint alone.
Mitigation direction
- Identify every WordPress site running GiveWP and record its installed version.
- Check GiveWP and Patchstack guidance for a confirmed patched release or vendor mitigation.
- Update beyond the affected range only after confirming the release is vendor-approved.
- Disable GiveWP on exposed sites if confirmed remediation cannot be applied promptly.
- Restrict external access where operationally feasible until remediation is confirmed.
Validation and detection
- Confirm GiveWP is absent or no affected version remains installed.
- Review web, WordPress, and hosting logs for suspicious unauthenticated requests or unexpected errors.
- Inspect affected hosts for unexplained file changes, accounts, plugins, scheduled tasks, or outbound connections.
- Run approved integrity and malware checks across WordPress files and the hosting environment.
- Verify the site and donation workflows function after remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-82222 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 10 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H3.96PatchstackVulnerability scoring details
Base CVSS 3.1 score
10CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/wordpress/plugin/give/vulnerability/wordpress-givewp-plugin-4-16-7-1-remote-code-execution-rce-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
- https://patchstack.com/articles/unauthenticated-php-object-injection-to-remote-code-execution-on-givewp?_s_id=cveCVE reference, Patchstack · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.