Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2024-9634 is a critical-severity Deserialization of Untrusted Data (CWE-502) vulnerability in Givewp Givewp. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 30% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
The GiveWP Donation Plugin and Fundraising Platform for WordPress is affected by a PHP Object Injection vulnerability (CWE-502) in all versions through 3.16.3. The flaw stems from unsafe deserialization of untrusted input supplied in the give_company_name parameter, which is processed in DonationRepository.php and related donation-handling code. When a suitable property-oriented programming (POP) chain is present, the injection leads directly to remote code execution.
Unauthenticated attackers can exploit the issue over the network by submitting a crafted donation request containing a serialized PHP object. Successful exploitation grants the attacker full control over the target WordPress site, including the ability to execute arbitrary code, read or modify data, and pivot within the hosting environment. The CVSS 3.1 base score of 9.8 reflects the absence of required authentication, user interaction, or special conditions.
The referenced Wordfence advisory and WordPress plugin changeset indicate that the issue was resolved in version 3.16.4 by updating the donation-processing logic in process-donation.php to prevent untrusted deserialization. Site administrators should upgrade immediately and verify that no custom code reintroduces similar object-injection paths. The EPSS score reached a peak of 0.2641 after disclosure before settling at 0.2278, indicating sustained but not explosive interest from attackers.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-50069
Vulnerability Data
The GiveWP – Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.16.3 via deserialization of untrusted input from the give_company_name parameter. This makes it possible for unauthenticated…
more
attackers to inject a PHP Object. The additional presence of a POP chain allows attackers to achieve remote code execution.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can uncover deserialization flaws before deployment.
Input validation directly stops deserialization of untrusted data by ensuring inputs are valid before processing.
Engineering principles such as safe deserialization and input sanitization structurally prevent the weakness from being introduced.
Integrity verification tools can detect malformed or tampered serialized data after the fact.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
PR.PS-02 addresses only post-deployment updates/patching and cannot prevent introduction of unsafe deserialization code, yet it can remediate some instances when the flaw exists in outdated libraries or components.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing includes validation of deserialization routines and the use of untrusted data, reducing the likelihood that unsafe object reconstruction will be deployed.
Requiring vetted libraries, regular updates and SAST before release reduces the likelihood that deserialization logic will accept and act on attacker-controlled serialized objects.
Regular scanning of third-party libraries and timely patching reduce the likelihood that unsafe deserialization vulnerabilities remain active.
Mandatory malware scanning of data received over networks or storage media intercepts malicious serialized payloads before they are deserialized by the target application.