LiveActive security incident?Get immediate response
CVE Record

CVE-2026-4703: WS Form LITE <= 1.10.80 - Unauthenticated PHP Object Injection via Form Submission

The WS Form LITE – Drag & Drop Contact Form Builder plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.10.80 via deserialization of untrusted input from form submission meta values. 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.

CriticalCVSS 9.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

WS Form LITE for WordPress through version 1.10.80 accepts unsafe data from unauthenticated form submissions. Serious compromise requires another installed plugin or theme providing a usable PHP object chain. Without that chain, the supplied sources report no impact; with one, data theft, file deletion, or code execution may be possible.

Executive priority

Treat this as an urgent patching and inventory task for public WordPress sites. Prioritize installations with many third-party plugins or themes because they are more likely to contain a usable object chain. The conditional exploit requirement reduces certainty of compromise, not the need to remediate.

Technical view

CVE-2026-4703 is a CWE-502 deserialization flaw in form-submission meta handling. An unauthenticated attacker can inject a PHP object. WS Form LITE itself reportedly contains no known POP chain, so harmful outcomes depend on a compatible chain in another installed plugin or theme. The CVSS 3.1 score is 9.8.

Likely exposure

Internet-accessible WordPress sites running WS Form LITE 1.10.80 or earlier are potentially exposed. Practical impact depends on whether installed plugins or themes supply a compatible POP chain. Sites without the plugin, running a later corrected release, or lacking such a chain have materially lower risk.

Exploitation context

The CVE is not listed as KEV in the supplied bundle, and no supplied source establishes active exploitation. This does not prove exploitation is absent. Attacks require unauthenticated form submission access plus a usable POP chain elsewhere on the affected WordPress installation.

Researcher notes

The supplied references identify vulnerable deserialization-related code and a WordPress changeset, but the bundle does not explicitly name a fixed release. Validate remediation against current official guidance. Assess the complete plugin and theme set for compatible POP chains; do not infer code execution from WS Form LITE alone.

Mitigation direction

  • Update WS Form LITE according to official WordPress or vendor guidance, ensuring version 1.10.80 or earlier is removed.
  • If updating is impossible, disable the plugin or affected public forms until remediation is confirmed.
  • Remove unnecessary plugins and themes to reduce potential PHP object-chain exposure.
  • Back up the site before remediation and protect backups from web-accessible modification.

Validation and detection

  • Inventory every WordPress site and record its installed WS Form LITE version.
  • Confirm no active installation remains at version 1.10.80 or earlier.
  • Review installed plugins and themes for known PHP deserialization gadget chains and outstanding security updates.
  • Verify affected forms no longer reach the vulnerable behavior after updating or disabling the plugin.
  • Review relevant application, file-integrity, and security logs for unexplained changes around form submissions.
Prepared
Confidence
high
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-4703 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
5Timeline events
1ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Wordfence

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-4703Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. Source timelineWordfence

    Vendor Notified

  3. Source timelineWordfence

    Disclosed

  4. CVE publishedCVE Program

    The CVE record was published.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
westguardWS Form LITE – Drag & Drop Contact Form Builder0unaffected
Weakness

CWE details

CWE-502

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs