Summary
CVE-2026-4703 is a critical PHP Object Injection vulnerability in the WS Form LITE – Drag & Drop Contact Form Builder plugin for WordPress, affecting all versions up to and including 1.10.80. The flaw arises from unsafe deserialization of untrusted input submitted through form submission meta values, and can be triggered by unauthenticated attackers over the network. It carries a CVSS v3.1 base score of 9.8 (Critical).
Technical details
- Root cause: the plugin deserializes untrusted data supplied in form submission meta values without adequate validation (CWE-502, Deserialization of Untrusted Data).
- Trigger condition: an attacker submits a crafted form on a site running the vulnerable plugin; no authentication or user interaction is required.
- Attack vector: network-based, exploitable remotely via standard form submission requests.
- Impact: by itself, the flaw allows arbitrary PHP object injection; actual severity depends on whether a POP (Property-Oriented Programming) chain exists in other plugins or themes installed on the same site. Where such a chain is present, impact can extend to file deletion, sensitive data exposure, or arbitrary code execution.
Affected software
- WS Form LITE – Drag & Drop Contact Form Builder (WordPress plugin), all versions up to and including 1.10.80.
Severity
- CVSS v3.1 Base Score: 9.8 (Critical)
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate: Update WS Form LITE to a patched version above 1.10.80 as soon as one is released by the vendor.
- If no patch is available: Restrict or disable public-facing form submission functionality until patched, monitor sites for unexpected PHP errors or unusual form submission payloads, and audit other installed plugins/themes for known deserialization (POP chain) gadgets that could be chained with this issue.
- General hardening: Keep WordPress core, plugins, and themes up to date, and apply the principle of least privilege to reduce the impact of any successful object injection.
How IONIX identifies potentially affected assets
IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.
- Raw response body:
/wp-content/plugins/ws-form/

