LiveActive security incident?Get immediate response
CVE Record

CVE-2021-42358: Contact Form With Captcha <= 1.6.2 Cross-Site Request Forgery to Reflected Cross-Site Scripting

The Contact Form With Captcha WordPress plugin is vulnerable to Cross-Site Request Forgery due to missing nonce validation in the ~/cfwc-form.php file during contact form submission, which made it possible for attackers to inject arbitrary web scripts in versions up to, and including 1.6.2.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This affects WordPress sites using the Contact Form With Captcha plugin up to version 1.6.2. A missing anti-CSRF check in form submission handling could let an attacker cause script injection in a user’s browser. The public bundle does not show active exploitation.

Executive priority

Treat as high priority for affected WordPress sites, especially public websites handling customer inquiries. The issue can affect confidentiality and integrity through browser-side script execution, but current evidence does not show confirmed active exploitation.

Technical view

CVE-2021-42358 is a CWE-352 CSRF issue in cfwc-form.php during contact form submission, leading to reflected XSS. The CVSS 3.1 score is 8.8 with network attack vector, low complexity, no privileges required, and user interaction required.

Likely exposure

Exposure is likely limited to WordPress sites with Contact Form With Captcha version 1.6.2 or earlier installed and reachable contact form functionality enabled.

Exploitation context

The CVE is not listed as KEV in the provided bundle. Exploitation requires user interaction, and the sources do not provide evidence of real-world exploitation or a public exploit.

Researcher notes

The source bundle identifies missing nonce validation in cfwc-form.php and classifies the weakness as CWE-352. It does not include a fixed version, patch details, or exploitation telemetry, so remediation should be tied to current vendor or trusted advisory guidance.

Mitigation direction

  • Inventory WordPress sites for Contact Form With Captcha installations.
  • Identify any plugin version 1.6.2 or earlier.
  • Check vendor or Wordfence guidance for fixed versions or mitigations.
  • Update, disable, or remove affected plugin deployments if no safe version is confirmed.
  • Review dependent contact-form workflows before disabling production forms.

Validation and detection

  • Confirm plugin presence and exact version on each WordPress site.
  • Verify whether cfwc-form.php exists in the installed plugin package.
  • Check public pages for active forms using this plugin.
  • Review security logs for suspicious form-submission patterns.
  • Confirm remediation by rechecking plugin version or removal status.
Prepared
Confidence
medium
Sources
4

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-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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-2021-42358 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
3Source 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-2021-42358Attack 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
Contact Form With CaptchaContact Form With Captcha1.6.2Listed
Weakness

CWE details

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

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.