CVE-2025-6742

SureForms – Drag and Drop Form Builder for WordPress <= 1.7.3 - Unauthenticated PHP Object Injection (PHAR) Triggered via Admin Submission Deletion

2025-07-08 17:20
Phat RiO

Strategic Overview

Status
Patched in 0.0.14
Affected Version
0.0 – 1.7.3 · 9 branches
CVSS
7.5High
Weakness type
CWE-502 · Deserialization of Untrusted Data
CVE
CVE-2025-6742
View all SureForms – Contact Form Builder, AI Forms, Payment Form, Survey & Quiz vulnerabilities

At a glance

CVE-2025-6742 is a high-severity Deserialization of Untrusted Data vulnerability in the SureForms WordPress plugin, affecting versions 0.0 – 1.7.3 · 9 branches. It carries a CVSS score of 7.5 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 0.0.14; sites on affected versions should update now. Disclosed July 2025, reported by Phat RiO.

Vulnerability Overview

The SureForms – Drag and Drop Form Builder for WordPress plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.7.3 via the use of file_exists() in the delete_entry_files() function without restriction on the path provided. This makes it possible for unauthenticated attackers to inject a PHP Object. 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.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no privileges on the target site. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-502: Deserialization of Untrusted Data

SureForms 0.0 – 1.7.3 · 9 branches carries this weakness at file_exists(), and reaching it takes no account at all. Deserialization of untrusted data means the application reconstructs objects from input a caller controls, letting the attacker choose which classes get instantiated and what their properties hold.

A workable chain turns deserialization into file writes, deletions or code execution, depending on what the loaded classes do in their magic methods. For SureForms the fix is 0.0.14: builds 0.0 – 1.7.3 · 9 branches are affected, anything from 0.0.14 onward is not.

Remediation

Update to one of the following versions, or a newer patched version: 0.0.14, 1.0.7, 1.1.2, 1.2.5, 1.3.2, 1.4.5, 1.5.1, 1.6.5, 1.7.4

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: SureForms 0.0.14 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C