Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-12877: CWE-502 Deserialization of Untrusted Data in webdevmattcrom GiveWP – Donation Plugin and Fundraising Platform

0
Critical
VulnerabilityCVE-2024-12877cvecve-2024-12877cwe-502
Published: Sat Jan 11 2025 (01/11/2025, 07:21:53 UTC)
Source: CVE Database V5
Vendor/Project: webdevmattcrom
Product: GiveWP – Donation Plugin and Fundraising Platform

Description

CVE-2024-12877 is a critical PHP Object Injection vulnerability in the GiveWP WordPress donation plugin versions up to 3. 19. 2. It arises from unsafe deserialization of untrusted input fields such as 'firstName' in the donation form, allowing unauthenticated attackers to inject malicious PHP objects. Exploiting this vulnerability enables attackers to delete arbitrary files on the server via a POP chain, potentially leading to remote code execution. Partial fixes in version 3. 19. 3 were insufficient, with a complete patch only available in 3. 19. 4.

AI-Powered Analysis

AILast updated: 02/26/2026, 02:40:47 UTC

Technical Analysis

CVE-2024-12877 is a critical vulnerability classified under CWE-502 (Deserialization of Untrusted Data) affecting the GiveWP – Donation Plugin and Fundraising Platform for WordPress. The flaw exists in all versions up to and including 3.19.2, where the plugin improperly deserializes user-supplied input from donation form fields such as 'firstName'. This unsafe deserialization allows unauthenticated attackers to perform PHP Object Injection, a technique where crafted serialized PHP objects are injected and executed. The presence of a Property Oriented Programming (POP) chain within the plugin's codebase enables attackers to leverage this injection to delete arbitrary files on the server filesystem. This file deletion capability can be chained to achieve remote code execution (RCE), granting full control over the affected server. Although version 3.19.3 attempted a partial fix, it was insufficient, and a fully effective patch was only released in version 3.19.4. The vulnerability has a CVSS v3.1 base score of 9.8, reflecting its critical severity with network attack vector, no privileges or user interaction required, and high impact on confidentiality, integrity, and availability. The recommended remediation includes upgrading to version 3.19.4 or later and adopting safer data handling practices such as JSON encoding to prevent unsafe deserialization. No known exploits are currently reported in the wild, but the severity and ease of exploitation make this a high-priority issue for organizations using the plugin.

Potential Impact

The impact of CVE-2024-12877 is severe for organizations using the GiveWP plugin on WordPress sites, particularly those handling donations and fundraising activities. Successful exploitation allows unauthenticated attackers to execute arbitrary PHP code remotely, leading to full server compromise. This can result in data breaches, defacement, loss of donor trust, disruption of fundraising operations, and potential financial fraud. The ability to delete arbitrary files further exacerbates the risk by enabling attackers to remove critical files, disrupt services, or implant backdoors. Given the plugin's widespread use in non-profit and fundraising sectors, the threat extends to organizations globally, potentially affecting sensitive donor information and critical fundraising infrastructure. The lack of authentication and user interaction requirements increases the likelihood of exploitation, making it a significant threat to availability, integrity, and confidentiality of affected systems.

Mitigation Recommendations

1. Immediate upgrade to GiveWP plugin version 3.19.4 or later, which contains the fully patched fix for this vulnerability. 2. If immediate upgrade is not feasible, implement web application firewall (WAF) rules to detect and block suspicious serialized PHP object payloads targeting the donation form inputs. 3. Disable or restrict PHP unserialize() usage in plugin code or server-wide if possible, or apply hardened deserialization libraries that enforce strict type whitelisting. 4. Employ input validation and sanitization on all user-supplied data, especially fields that are deserialized. 5. Monitor server logs for unusual file deletion activities or unexpected PHP object injection attempts. 6. Consider isolating the WordPress environment and limiting file system permissions to minimize damage from potential exploitation. 7. Encourage the vendor to adopt safer data encoding formats such as JSON to prevent future deserialization vulnerabilities. 8. Regularly audit and update all WordPress plugins and themes to reduce exposure to known vulnerabilities.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2024-12-20T21:49:42.876Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6e4bb7ef31ef0b59c70a

Added to database: 2/25/2026, 9:48:59 PM

Last enriched: 2/26/2026, 2:40:47 AM

Last updated: 2/26/2026, 7:40:23 AM

Views: 2

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats