high CVSS 7.2

CVE-2025-0429·PHP vulnerability

The "AI Power: Complete AI Pack" plugin for WordPress is vulnerable to PHP Object Injection in versions up to, and including, 1.8.96 via deserialization of untrusted input from the $form['post_content'] variable through the wpaicg_export_ai_forms() function. This allows authenticated attackers, with administrative privileges, to inject a PHP Object. No POP chain is present in the vulnerable plugin. 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
1.8.97
Published
2025-01-22

Affected versions

Until: 1.8.97

Fixed in: 1.8.97

How to fix this CVE

Update the 'AI Power: Complete AI Pack' WordPress plugin to version 1.8.97 or later to patch the PHP object injection vulnerability. This flaw allows administrators to inject malicious PHP objects through the form export functionality, which could lead to arbitrary file deletion, data theft, or code execution if a gadget chain exists in your WordPress environment. Immediately audit any recent plugin exports or administrative activity in your WordPress audit logs.

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. 

Implement a WAF rule to block POST requests to wp-admin/admin-ajax.php with action=wpaicg_export_ai_forms that contain serialized PHP object patterns (e.g., strings matching O:\d+:"[^"]+":). Monitor for base64-encoded serialized objects in form POST data.

How to check if you are affected

  1. Check installed PHP version: php -v
  2. Verify the 'AI Power: Complete AI Pack' plugin version in WordPress dashboard: Plugins > Installed Plugins, look for 'AI Power' and note the version number
  3. Search WordPress error logs for deserialization warnings: grep -i 'unserialize\|object injection' /var/log/wordpress/*.log or check wp-content/debug.log if WP_DEBUG_LOG is enabled
  4. Confirm the patch by checking plugin version again after update: grep -r 'Version:' /path/to/wp-content/plugins/ai-power-* | head -1

FAQ

What is CVE-2025-0429?

CVE-2025-0429 is a PHP object injection vulnerability in the 'AI Power: Complete AI Pack' WordPress plugin that allows authenticated administrators to deserialize untrusted data through the form export feature, potentially enabling arbitrary file operations or code execution if additional vulnerable components exist on the server.

Is CVE-2025-0429 being actively exploited?

No, this vulnerability is not currently listed in the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits have been disclosed. However, it poses a significant risk in multi-plugin environments where gadget chains may exist.

What versions of PHP are affected by CVE-2025-0429?

'AI Power: Complete AI Pack' plugin versions up to and including 1.8.96 are affected. The vulnerability is fixed in version 1.8.97 and later. This is a plugin vulnerability, not a PHP core vulnerability, though it requires PHP to execute.

How do I check if my server is vulnerable to CVE-2025-0429?

In the WordPress admin panel, navigate to Plugins > Installed Plugins and locate 'AI Power: Complete AI Pack'. If the version number is 1.8.96 or lower, your installation is vulnerable. Run: grep 'Version:' /wp-content/plugins/ai-power-complete-ai-pack/ai-power.php to verify from the command line.

Does Defensia detect CVE-2025-0429?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the 'AI Power: Complete AI Pack' plugin is detected on a monitored WordPress server, CVE-2025-0429 will appear in your dashboard with remediation steps and version guidance.

Related PHP CVEs

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

Get started free