high CVSS 7.5

CVE-2025-6464·PHP vulnerability

The Forminator Forms – Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.44.2 via deserialization of untrusted input in the 'entry_delete_upload_files' function. This makes it possible for unauthenticated attackers to inject a PHP Object through a PHAR file. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present. Deserialization occurs when the form submission is deleted, whether by an Administrator or via auto-deletion determined by plugin settings.

Severity
high
Software
PHP
Fixed in
1.44.3
Published
2025-07-02

Affected versions

Until: 1.44.3

Fixed in: 1.44.3

How to fix this CVE

Update the Forminator Forms plugin to version 1.44.3 or later to eliminate the PHP Object Injection vulnerability in the entry deletion handler. If you cannot update immediately and other plugins with known POP chains are installed, consider disabling auto-deletion of form entries and manually review file upload handling. Ensure all WordPress plugins and themes are kept current, as this vulnerability requires a secondary POP chain to be exploitable.

sudo dnf update php php-cli php-common php-curl php-fpm php-mysqlnd php-xml

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 Web Application Firewall rule to block HTTP POST requests to form entry deletion endpoints containing serialized PHP object markers (detect strings like 'O:' followed by digit patterns) and PHAR stream protocol references ('phar://'). Additionally, restrict uploads to known-safe file types and validate MIME types server-side.

How to check if you are affected

  1. Check installed Forminator plugin version: Log into WordPress admin > Plugins > Installed Plugins, locate Forminator, and verify the current version is below 1.44.3
  2. Review active WordPress plugins for known POP chain gadgets: Use wp-cli command `wp plugin list --status=active` and cross-reference each plugin against public POP chain databases
  3. Search web server logs for suspicious form entry deletion requests: `grep -i 'entry_delete_upload_files\|forminator.*phar' /var/log/apache2/access.log /var/log/nginx/access.log`
  4. Verify Forminator update completion: Log into WordPress admin > Plugins and confirm Forminator version is 1.44.3 or higher, then check plugin changelog in wp-content/plugins/forminator/readme.txt

FAQ

What is CVE-2025-6464?

This is a PHP Object Injection flaw in the Forminator WordPress plugin's form entry deletion function that allows deserialization of untrusted PHAR file data. The vulnerability has limited impact on its own but can enable serious attacks if complementary gadget chains exist in other installed plugins.

Is CVE-2025-6464 being actively exploited?

No, CVE-2025-6464 is not currently listed on the CISA Known Exploited Vulnerabilities catalog, and no public exploits have been disclosed. However, organizations should still prioritize patching given the high CVSS score and the potential for exploitation in environments with vulnerable plugin combinations.

What versions of Forminator are affected by CVE-2025-6464?

All versions of the Forminator Forms plugin up to and including version 1.44.2 are vulnerable. Version 1.44.3 and later contain the fix.

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

Use the WordPress CLI to check the installed Forminator version: `wp plugin get forminator --field=version`. If the output is 1.44.2 or lower, your site is vulnerable and requires immediate updating.

Does Defensia detect CVE-2025-6464?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Forminator is installed on a monitored WordPress site, CVE-2025-6464 will appear in your dashboard with remediation steps and risk scoring.

Related PHP CVEs

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

Get started free