LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32496: WordPress Spam Protect for Contact Form 7 plugin <= 1.2.9 - Arbitrary File Deletion vulnerability

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in NYSL Spam Protect for Contact Form 7 wp-contact-form-7-spam-blocker allows Path Traversal.This issue affects Spam Protect for Contact Form 7: from n/a through <= 1.2.9.

MediumCVSS 6.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-32496 affects the WordPress plugin Spam Protect for Contact Form 7 through version 1.2.9. A high-privileged user could abuse path traversal to delete arbitrary files, potentially disrupting the site. This is not listed as known exploited in the provided sources.

Executive priority

Treat as a moderate-priority WordPress exposure. It is most urgent for sites where many administrators exist, privileged accounts are weakly controlled, or uptime is critical. Prioritize inventory and removal or update decisions.

Technical view

The issue is CWE-22 path traversal in NYSL wp-contact-form-7-spam-blocker. CVSS 3.1 is 6.8: network reachable, low complexity, high privileges required, no user interaction, changed scope, and high availability impact. The reported impact is arbitrary file deletion.

Likely exposure

Exposure is limited to WordPress sites with Spam Protect for Contact Form 7 installed at version 1.2.9 or earlier. Risk depends heavily on who has high-privileged WordPress access and whether the plugin is active.

Exploitation context

The CVSS vector indicates exploitation requires high privileges but no user interaction. The source bundle does not show CISA KEV listing, active exploitation, exploit code, or a confirmed fixed version.

Researcher notes

Available evidence identifies affected versions and impact but does not provide patch status or exploitation evidence. Avoid assuming unauthenticated exploitation; the CVSS vector specifies high privileges required. Validate exposure by plugin slug and version.

Mitigation direction

  • Inventory WordPress sites for wp-contact-form-7-spam-blocker version 1.2.9 or earlier.
  • Check vendor, WordPress plugin, or Patchstack guidance for a fixed release.
  • Disable or remove the plugin if it is not business-critical.
  • Restrict and audit high-privileged WordPress accounts.
  • Maintain recent, restorable backups for affected WordPress sites.

Validation and detection

  • Confirm whether the plugin is installed and active.
  • Record the installed plugin version on each WordPress site.
  • Flag version 1.2.9 or earlier as affected.
  • Review privileged WordPress user accounts for necessity.
  • Check site logs and integrity monitoring for unexpected file deletion.
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-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection 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
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-32496 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
Medium
CVSS
6.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:N/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
6.8CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H2.34Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.8Medium
CVSS 3.1 vector shape for CVE-2026-32496Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:N/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
NYSLSpam Protect for Contact Form 7wp-contact-form-7-spam-blocker, n/aunaffected
Weakness

CWE details

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

CWE-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.