medium CVSS 6.6 EPSS 0.43%

CVE-2024-9529·PHP vulnerability

The Secure Custom Fields WordPress plugin before 6.3.9, Secure Custom Fields WordPress plugin before 6.3.6.3, Advanced Custom Fields Pro WordPress plugin before 6.3.9 does not prevent users from running arbitrary functions through its setting import functionalities, which could allow high privilege users such as admin to run arbitrary PHP functions.

Severity
medium
Software
PHP
Fixed in
6.3.9
Published

How likely is exploitation

FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.43% — higher than 36% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.

Affected versions

Until: 6.3.9

Fixed in: 6.3.9

How to fix this CVE

Update PHP and the affected Custom Fields WordPress plugins (Secure Custom Fields and Advanced Custom Fields Pro) to version 6.3.9 or later to close the arbitrary function execution vulnerability in the settings import feature. This vulnerability allows high-privilege WordPress administrators to bypass security controls and execute unauthorized PHP functions during plugin configuration imports. Immediately review and restrict admin-level access on affected WordPress installations until the patch is applied.

sudo dnf update 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. 

Block or require additional authentication for POST requests to WordPress admin endpoints containing 'acf' or 'import' parameters; implement strict Content-Security-Policy headers to prevent unexpected function execution in the wp-admin context.

How to check if you are affected

  1. Step 1: Check PHP version with `php -v` and note the installed version number
  2. Step 2: Verify WordPress plugin versions by accessing wp-admin > Plugins and checking 'Secure Custom Fields' and 'Advanced Custom Fields Pro' versions against 6.3.9
  3. Step 3: Search WordPress database logs and webserver access logs for POST requests to `/wp-admin/admin.php?page=acf-settings` or similar ACF settings import endpoints from admin users
  4. Step 4: Run `php -v` again after patching and confirm the updated version is active; restart PHP-FPM or Apache with `sudo systemctl restart php-fpm` or equivalent to activate the patch

FAQ

What is CVE-2024-9529?

This vulnerability affects WordPress plugins that handle custom field configurations and allows administrative users to execute arbitrary PHP functions during settings import without proper validation, potentially leading to unauthorized code execution and system compromise.

Is CVE-2024-9529 being actively exploited?

No, CVE-2024-9529 is not listed on the CISA Known Exploited Vulnerabilities catalog and no public exploits are currently available, though exploitation is theoretically possible by authenticated admin accounts.

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

All versions of PHP used with Secure Custom Fields versions before 6.3.9 and Advanced Custom Fields Pro versions before 6.3.9 are affected; the vulnerability is in the plugin code, not PHP itself.

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

Run `wp plugin list` in your WordPress root directory to display installed plugins and their versions; if Secure Custom Fields or Advanced Custom Fields Pro shows a version below 6.3.9, your installation is vulnerable.

Does Defensia detect CVE-2024-9529?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If PHP is installed on a monitored server, CVE-2024-9529 will appear in your dashboard with remediation steps.

Related PHP CVEs

CVE-2026-39337CVSS 10ChurchCRM is an open-source church management system. Prior to 7.1.0, critical 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 "$dbPassword" variable is not sanitized. This vulnerability exists due to an incomplete fix for CVE-2025-62521. This vulnerability is fixed in 7.1.0.
CVE-2026-28289CVSS 10FreeScout is a free help desk and shared inbox built with PHP's Laravel framework. A patch bypass vulnerability for CVE-2026-27636 in FreeScout 1.8.206 and earlier allows any authenticated user with file upload permissions to achieve Remote Code Execution (RCE) on the server by uploading a malicious .htaccess file using a zero-width space character prefix to bypass the security check. The vulnerability exists in the sanitizeUploadedFileName() function in app/Http/Helper.php. The function contains a Time-of-Check to Time-of-Use (TOCTOU) flaw where the dot-prefix check occurs before sanitization removes invisible characters. This vulnerability is fixed in 1.8.207.
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-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.

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-9529. Free for 1 server.

Get started free