Skip to main content
COSMICBYTEZLABS
NewsSecurityHOWTOsToolsTraining
StudyProjectsNewsletterHire MeAbout
Subscribe

Press Enter to search or Esc to close

News
Security
HOWTOs
Tools
Training
Study
Projects
Newsletter
Hire Me
About
RSS Feed
Reading List
Subscribe

Stay in the Loop

Get the latest security alerts, tutorials, and tech insights delivered to your inbox.

Subscribe NowFree forever. No spam.
COSMICBYTEZLABS

Your trusted source for IT intelligence, cybersecurity insights, and hands-on technical guides.

2579+ Articles
161+ Guides

CONTENT

  • Latest News
  • Security Alerts
  • HOWTOs
  • Checklists
  • Projects
  • Exam Prep

RESOURCES

  • Search
  • Browse Tags
  • Newsletter Archive
  • Reading List
  • RSS Feed

COMPANY

  • About Us
  • Contact
  • Privacy Policy
  • Terms of Service

© 2026 CosmicBytez Labs. All rights reserved.

System Status: Operational
  1. Home
  2. News
  3. Critical GiveWP Flaw Lets Hackers Run Server Commands
Critical GiveWP Flaw Lets Hackers Run Server Commands
NEWS

Critical GiveWP Flaw Lets Hackers Run Server Commands

CVE-2026-82222 chains PHP object injection and an auth-bypass bug in GiveWP, letting attackers run OS commands on 100,000+ WordPress donation sites.

Dylan H.

News Desk

August 29, 2026
4 min read

What Happened

A maximum-severity vulnerability in GiveWP, a WordPress donation and fundraising plugin with more than 100,000 active installs, allows attackers to execute arbitrary commands on the hosting server. Tracked as CVE-2026-82222, the flaw affects GiveWP through version 4.16.7.1 and was fixed in 4.16.7.2, released August 27, 2026. It was reported through Patchstack on July 28 by researcher Udin Chan.


Incident Details

AttributeValue
CVE IDCVE-2026-82222
Affected PluginGiveWP — Donation Plugin and Fundraising Platform
Affected VersionsThrough 4.16.7.1
Fixed Version4.16.7.2 (released August 27, 2026)
Active Installs100,000+
Vulnerability ClassPHP Object Injection chained to Remote Code Execution
Reported ByUdin Chan, via Patchstack
Disclosure DateReported July 28, patched August 27

How It Works

The Vulnerability Chain

The flaw isn't a single bug but a chain of three separate issues: an unsafe PHP safeUnserialize() helper that fails to properly restrict deserialization, GiveWP's donation-processing flow storing attacker-controlled serialized objects in the database, and a gadget chain in libraries bundled with the plugin that turns that unsafe deserialization into arbitrary operating-system command execution. On version 4.16.5.1 and earlier, a default installation with any published donation form and an active payment gateway is enough on its own to be exploitable. Versions 4.16.6 through 4.16.7.1 narrowed the attack path but did not close the underlying deserialization flaw.

The Authentication Bypass

Exploiting the object-injection chain normally requires an authenticated account on the target WordPress site. GiveWP closes that gap for attackers on its own: Patchstack found the plugin exposes an unauthenticated registration action (give_action=user_register) that never checks WordPress's users_can_register setting — meaning an attacker can create an account and proceed with the exploit chain even on sites that have registration explicitly disabled.

The Fix

GiveWP's 4.16.7.2 update blocks serialized data from being accepted during donation processing, restricts object creation at the deserialization points involved in the chain, and ships a database migration that scrubs any malicious serialized objects that may already have been stored from prior exploitation attempts. The unauthenticated registration action itself was not removed in this release, though Patchstack notes it can no longer be chained into RCE once the object-injection path is closed.


Impact Assessment

Impact AreaDescription
Server CompromiseFull command execution in the context of the web server — file access, malware installation, and pivoting into the wider hosting environment
ScaleOver 100,000 active WordPress sites run GiveWP, many of them nonprofit and donation-collecting organizations
AuthenticationEffectively unauthenticated in practice, due to the unauthenticated registration bypass — registration being "disabled" does not block exploitation
Prior HistoryGiveWP has had multiple PHP object injection CVEs since 2024 (CVE-2025-0912, CVE-2025-22777, CVE-2024-5932); a related 2024 GiveWP compromise indirectly exposed 30,000 Pi-hole donor records

Recommendations

For GiveWP Site Administrators

  • Update to GiveWP 4.16.7.2 or later immediately — this is a critical, effectively unauthenticated remote code execution chain.
  • Review the site's user list for any unexpected accounts created via the registration bypass, even on sites where registration was believed to be disabled.
  • Check server and application logs for unusual outbound connections, unexpected file writes, or new admin/database changes dated after July 28 (the report date), in case exploitation occurred before the patch.

For WordPress Hosts and Agencies Managing Client Sites

  • Treat this as a priority patch across any managed WordPress fleet running GiveWP, given the plugin's install base and the plugin's recurring history of object-injection vulnerabilities.
  • Consider a web application firewall rule blocking unauthenticated requests to give_action=user_register as a stopgap on sites that cannot be patched immediately.

Key Takeaways

  1. CVE-2026-82222 chains PHP object injection, unsafe deserialization, and a bundled gadget chain into full remote code execution in GiveWP.
  2. A separate unauthenticated registration bypass (give_action=user_register) lets attackers create accounts even when registration is disabled, removing the usual authentication barrier.
  3. Versions through 4.16.7.1 are affected; 4.16.7.2 (August 27, 2026) fixes the issue and scrubs malicious data via a database migration.
  4. Over 100,000 active installs are exposed, many belonging to nonprofits and fundraising organizations.
  5. GiveWP has a recurring history of PHP object injection flaws dating back to 2024, including a prior incident that indirectly exposed 30,000 Pi-hole donor records.
  6. Site administrators should update immediately and audit for unexpected user accounts created before patching.

Sources

  • BleepingComputer — GiveWP WordPress donation plugin flaw lets hackers execute server commands
  • Patchstack — Critical Vulnerability Patched in GiveWP Plugin
#GiveWP#WordPress#PHP Object Injection#Remote Code Execution#Patchstack#CVE-2026-82222

Related Articles

WordPress ARForms Plugin Critical PHP Object Injection — CVE-2024-13784

A critical unauthenticated PHP object injection flaw in the ARForms WordPress plugin (CVSS 9.8) allows arbitrary code execution via deserialization.

3 min read

CVE-2026-28139: Critical PHP Object Injection in Ajax Search Lite

A CVSS 9.8 unauthenticated PHP object injection flaw in Ajax Search Lite <= 4.14.4 exposes 80,000+ WordPress sites to potential remote code execution via POP chain gadgets.

6 min read

Critical PHP Object Injection in FundEngine Plugin (CVE-2026-32470)

An unauthenticated PHP Object Injection flaw (CVSS 9.8) in FundEngine <= 1.7.9 allows remote attackers to execute arbitrary code without credentials.

3 min read
Back to all News