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-2025-13486: CWE-94 Improper Control of Generation of Code ('Code Injection') in hwk-fr Advanced Custom Fields: Extended

0
Critical
VulnerabilityCVE-2025-13486cvecve-2025-13486cwe-94
Published: Wed Dec 03 2025 (12/03/2025, 06:47:46 UTC)
Source: CVE Database V5
Vendor/Project: hwk-fr
Product: Advanced Custom Fields: Extended

Description

The Advanced Custom Fields: Extended plugin for WordPress is vulnerable to Remote Code Execution in versions 0.9.0.5 through 0.9.1.1 via the prepare_form() function. This is due to the function accepting user input and then passing that through call_user_func_array(). This makes it possible for unauthenticated attackers to execute arbitrary code on the server, which can be leveraged to inject backdoors or create new administrative user accounts.

AI-Powered Analysis

AILast updated: 12/03/2025, 07:02:15 UTC

Technical Analysis

CVE-2025-13486 is a critical remote code execution (RCE) vulnerability affecting the Advanced Custom Fields: Extended plugin for WordPress, specifically versions 0.9.0.5 through 0.9.1.1. The vulnerability stems from the prepare_form() function, which improperly handles user input by passing it directly to PHP's call_user_func_array() without sufficient validation or sanitization. This CWE-94 (Improper Control of Generation of Code) weakness allows unauthenticated attackers to inject and execute arbitrary PHP code on the server hosting the WordPress site. Because the function is accessible without authentication and requires no user interaction, exploitation is straightforward. Successful exploitation can lead to full system compromise, including the installation of persistent backdoors, creation of new administrative user accounts, and complete control over the website and potentially the underlying server. The vulnerability carries a CVSS v3.1 score of 9.8 (critical), reflecting its high impact on confidentiality, integrity, and availability, combined with low attack complexity and no privileges required. Although no public exploits have been reported yet, the nature of the flaw and the popularity of WordPress make it a prime target for attackers. The lack of available patches at the time of disclosure further increases the urgency for mitigation.

Potential Impact

For European organizations, this vulnerability poses a severe risk due to the widespread use of WordPress for corporate websites, intranets, and e-commerce platforms. Exploitation can lead to unauthorized access to sensitive data, including personal customer information protected under GDPR, resulting in regulatory penalties and loss of customer trust. Attackers could deface websites, disrupt services, or use compromised servers as pivot points for further attacks within the organization's network. The ability to create administrative accounts or install backdoors means long-term persistence and potential lateral movement. This can severely impact business continuity, brand reputation, and compliance posture. Organizations in sectors such as finance, healthcare, government, and e-commerce are particularly at risk due to the sensitivity of their data and the criticality of their online presence.

Mitigation Recommendations

Given the absence of an official patch at the time of disclosure, European organizations should immediately implement the following mitigations: 1) Disable or remove the Advanced Custom Fields: Extended plugin if it is not essential. 2) Restrict access to the WordPress admin and plugin directories via web server configuration or firewall rules to limit exposure to unauthenticated requests targeting the vulnerable function. 3) Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious requests invoking the prepare_form() function or unusual call_user_func_array() usage patterns. 4) Monitor server and application logs for signs of exploitation attempts, such as unexpected PHP function calls or new administrative user creation. 5) Regularly back up WordPress sites and databases to enable rapid restoration in case of compromise. 6) Follow vendor channels closely for patches or updates and apply them immediately upon release. 7) Conduct security audits and penetration tests focusing on plugin vulnerabilities and code injection risks. These targeted actions go beyond generic advice and address the specific exploitation vector of this vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-11-20T17:33:07.800Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 692fdfe670961fbaa28b6194

Added to database: 12/3/2025, 6:59:50 AM

Last enriched: 12/3/2025, 7:02:15 AM

Last updated: 12/3/2025, 9:06:08 AM

Views: 80

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 enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats