Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-4703 – PHP Object Injection – WS Form LITE WordPress Plugin (≤ 1.10.80)

Be the first to know when new zero-days emerge:

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/

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge