high CVSS 8.8

CVE-2024-8922·PHP vulnerability

The Product Enquiry for WooCommerce, WooCommerce product catalog plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 2.2.33.32 via deserialization of untrusted input in enquiry_detail.php. This makes it possible for authenticated attackers, with Author-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.

Severity
high
Software
PHP
Fixed in
2.2.33.34
Published
2024-09-27

Affected versions

Until: 2.2.33.34

Fixed in: 2.2.33.34

How to fix this CVE

Update the Product Enquiry for WooCommerce plugin to version 2.2.33.34 or later to patch the PHP Object Injection vulnerability in the enquiry_detail.php file. This vulnerability allows authenticated users with Author-level access to inject malicious PHP objects that could be exploited if additional vulnerable code exists in other plugins or themes. Immediately audit your WordPress environment for any suspicious object serialization activity and review user permissions to restrict Author-level access where unnecessary.

sudo dnf upgrade php

Defensia detects this vulnerability

WAF mitigation (if patching is not yet possible)

Add this rule to your WAF to block exploitation attempts while you schedule the patch. 

Implement WAF rules to block POST requests to enquiry_detail.php containing serialized PHP object patterns (e.g., 'O:' or 'a:' followed by numeric type indicators). Monitor for requests containing common gadget chain indicators such as '__wakeup', '__destruct', '__toString', or 'eval(' within POST parameters.

How to check if you are affected

  1. Step 1: Check PHP version with: php -v
  2. Step 2: For WordPress installations, verify the Product Enquiry for WooCommerce plugin version by navigating to Plugins > Installed Plugins and checking if version 2.2.33.34 or higher is installed
  3. Step 3: Search WordPress debug.log for serialized object patterns: grep -i 'unserialize\|serialize\|__wakeup\|__destruct' /path/to/wp-content/debug.log
  4. Step 4: After updating, confirm the plugin version in WordPress admin panel shows 2.2.33.34 or later and verify no errors appear in wp-admin

FAQ

What is CVE-2024-8922?

This is a PHP Object Injection vulnerability in the Product Enquiry for WooCommerce plugin that allows attackers with Author-level WordPress access to deserialize untrusted input through enquiry_detail.php. If other vulnerable code components exist in the environment, this could lead to file deletion, data theft, or remote code execution.

Is CVE-2024-8922 being actively exploited?

No, according to CISA's Known Exploited Vulnerabilities catalog, this CVE is not currently being actively exploited in the wild, and no public exploits have been released.

What versions of PHP are affected by CVE-2024-8922?

All versions of the Product Enquiry for WooCommerce plugin up to and including 2.2.33.32 are vulnerable. The vulnerability was patched in version 2.2.33.34.

How do I check if my server is vulnerable to CVE-2024-8922?

In your WordPress admin dashboard, navigate to Plugins > Installed Plugins and locate 'Product Enquiry for WooCommerce.' If the version number is 2.2.33.32 or lower, your installation is vulnerable. Update immediately to 2.2.33.34 or higher.

Does Defensia detect CVE-2024-8922?

Yes — Defensia's CVE advisory scanner compares installed WordPress plugin versions against the NVD database. If the vulnerable Product Enquiry for WooCommerce plugin is active on a monitored server, CVE-2024-8922 will appear in your dashboard with remediation steps.

Related PHP CVEs

CVE-2025-47916CVSS 10Invision Community 5.0.0 before 5.0.7 allows remote code execution via crafted template strings to themeeditor.php. The issue lies within the themeeditor controller (file: /applications/core/modules/front/system/themeeditor.php), where a protected method named customCss can be invoked by unauthenticated users. This method passes the value of the content parameter to the Theme::makeProcessFunction() method; hence it is evaluated by the template engine. Accordingly, this can be exploited by unauthenticated attackers to inject and execute arbitrary PHP code by providing crafted template strings.
CVE-2025-25174CVSS 10Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in beeteam368 BeeTeam368 Extensions beeteam368-extensions allows PHP Local File Inclusion.This issue affects BeeTeam368 Extensions: from n/a through <= 1.9.4.
CVE-2025-46348CVSS 10YesWiki is a wiki system written in PHP. Prior to version 4.5.4, the request to commence a site backup can be performed and downloaded without authentication. The archives are created with a predictable filename, so a malicious user could create and download an archive without being authenticated. This could result in a malicious attacker making numerous requests to create archives and fill up the file system, or by downloading the archive which contains sensitive site information. This issue has been patched in version 4.5.4.
CVE-2024-5932CVSS 10The GiveWP – Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.14.1 via deserialization of untrusted input from the 'give_title' parameter. This makes it possible for unauthenticated attackers to inject a PHP Object. The additional presence of a POP chain allows attackers to execute code remotely, and to delete arbitrary files.
CVE-2025-62521CVSS 10ChurchCRM is an open-source church management system. Prior to version 5.21.0, a pre-authentication remote code execution vulnerability in ChurchCRM's setup wizard allows unauthenticated attackers to inject arbitrary PHP code during the initial installation process, leading to complete server compromise. The vulnerability exists in `setup/routes/setup.php` where user input from the setup form is directly concatenated into a PHP configuration template without any validation or sanitization. Any parameter in the setup form can be used to inject PHP code that gets written to `Include/Config.php`, which is then executed on every page load. This is more severe than typical authenticated RCE vulnerabilities because it requires no credentials and affects the installation process that administrators must complete. Version 5.21.0 patches the issue.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-8922. Free for 1 server.

Get started free