CWE Reference

CWE-352: Cross-Site Request Forgery

Official CWE-352 CWE context with Glexia analysis, remediation guidance, related CVEs, and ATT&CK context.

Release starter-2026-05weaknessDraft

Glexia's Take

CWE-352: Cross-Site Request Forgery

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

Executive Impact

Unauthorized state changes
Account setting changes
Forced transactions

Developer Pattern

CWE-352 is the kind of defect developers can usually prevent with explicit validation, safer framework defaults, and tests that exercise hostile input or unsafe state transitions.

Confidence

medium confidence from CWE-352, starter-2026-05.

Official CWE Definition

CWE-352: Cross-Site Request Forgery

Cross-Site Request Forgery is a software weakness pattern tracked by CWE 352. The local starter record is replaced by the official MITRE CWE import when the sync pipeline runs.

Type: weakness
Abstraction: Compound
Status: Draft
Source: MITRE CWE definition

Developer And Remediation Guidance

How teams prevent and detect this weakness

Causes

A state-changing POST endpoint accepts ambient cookies without CSRF protection.

Remediation

SameSite cookies
CSRF tokens
Origin validation
Re-authentication for sensitive actions

Detection

Manual testing
Code review
DAST

Mappings

Related CVEs, CWEs, and ATT&CK context

Related CWEs

No related CWE relationships are published yet.

Related CVEs

Related CVE mappings appear after CVE records are cross-indexed.

Open CWE CVE mapping

ATT&CK Relevance

ATT&CK relevance is shown only when reviewed or responsibly inferred.