LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32484: WordPress weForms plugin <= 1.6.26 - PHP Object Injection vulnerability

Deserialization of Untrusted Data vulnerability in BoldGrid weForms weforms allows Object Injection.This issue affects weForms: from n/a through <= 1.6.26.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-32484 affects the WordPress weForms plugin up to version 1.6.26. It is a PHP object injection issue caused by unsafe deserialization. If successfully exploited, the reported impact is high across confidentiality, integrity, and availability. The provided sources do not confirm active exploitation or name a fixed version.

Executive priority

Prioritize identifying affected WordPress sites this week. The severity is high, but urgency is tempered by no confirmed active exploitation in the provided sources and no named fixed version. Internet-facing sites handling sensitive form data should be addressed first.

Technical view

The vulnerability is CWE-502, Deserialization of Untrusted Data, in BoldGrid weForms. The CVSS 3.1 score is 8.8 with network attack vector, low complexity, no privileges required, and user interaction required. Affected versions are listed as weForms through 1.6.26. The source bundle does not include exploit details, indicators, or remediation specifics.

Likely exposure

Internet-facing WordPress sites using the weForms plugin version 1.6.26 or earlier are the primary exposure. Sites without weForms, or with versions outside the affected range, are not indicated as affected by the provided sources.

Exploitation context

No CISA KEV listing is reported, and the provided sources do not state active exploitation. The CVSS vector indicates exploitation is network-reachable, low complexity, requires no prior authentication, but does require user interaction.

Researcher notes

Evidence is limited to CVE metadata and Patchstack’s vulnerability entry. The key unknowns are fixed version, proof-of-concept status, affected code path, and required user interaction details. Avoid assuming remote code execution unless vendor or researcher sources confirm gadget-chain impact.

Mitigation direction

  • Inventory WordPress sites for the weForms plugin and record installed versions.
  • If weForms is version 1.6.26 or earlier, treat the site as exposed.
  • Check Patchstack, CVE, and vendor guidance for a fixed release or official mitigation.
  • Update weForms if a vendor-supported fixed version is available.
  • If no fix is available, consider disabling or removing the plugin where business impact allows.

Validation and detection

  • Confirm the plugin name is weForms and the installed version is 1.6.26 or earlier.
  • Review WordPress administrative plugin inventory across production, staging, and backups.
  • Monitor vendor and Patchstack pages for updated remediation details.
  • Review web and application logs for unusual activity around forms or plugin endpoints.
  • Document compensating controls if the plugin cannot be updated or removed.
Prepared
Confidence
medium
Sources
3

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-32484 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
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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
0Timeline events
0ADP providers
2Source links

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
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2026-32484Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
BoldGridweFormsweforms, n/aunaffected
Weakness

CWE details

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.