LiveActive security incident?Get immediate response
CVE Record

CVE-2021-39202: WordPress 5.8 beta: Stored Cross-Site Scripting (XSS) vulnerability in widget

WordPress is a free and open-source content management system written in PHP and paired with a MySQL or MariaDB database. In affected versions the widgets editor introduced in WordPress 5.8 beta 1 has improper handling of HTML input in the Custom HTML feature. This leads to stored XSS in the custom HTML widget. This has been patched in WordPress 5.8. It was only present during the testing/beta phase of WordPress 5.8.

HighCVSS 7.6Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This was a stored XSS flaw in the Custom HTML widget added during WordPress 5.8 beta testing. Affected sites were limited to WordPress 5.8 beta 1 and beta 2. WordPress says it was patched in 5.8 and only present during the beta phase.

Executive priority

Treat as a targeted cleanup item, not a broad emergency, unless the organization ran WordPress 5.8 beta builds on public sites. Confirm version exposure and upgrade status quickly.

Technical view

Improper handling of HTML input in the WordPress 5.8 beta widgets editor allowed stored cross-site scripting in the Custom HTML widget. CVSS 3.1 is 7.6 with network access, low complexity, low privileges, required user interaction, and changed scope.

Likely exposure

Exposure should be narrow: WordPress sites that publicly deployed 5.8 beta 1 or 5.8 beta 2. Stable WordPress 5.8 is listed as patched. Production sites that avoided beta releases are unlikely to be affected based on the provided sources.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. The vulnerability could matter where untrusted or compromised low-privilege users could store Custom HTML widget content that later reaches another user’s browser.

Researcher notes

Evidence is strongest for beta-only exposure and a stable-version patch. The public bundle does not provide exploit-in-the-wild evidence. Validation should focus on historical beta deployment, widget-edit permissions, and stored Custom HTML content integrity.

Mitigation direction

  • Upgrade any WordPress 5.8 beta 1 or beta 2 instance to WordPress 5.8 stable or later.
  • Remove beta WordPress builds from public production environments.
  • Restrict widget editing to trusted users until upgrade status is confirmed.
  • Review and clean Custom HTML widget content created during beta testing.
  • Check WordPress vendor guidance for any environment-specific remediation notes.

Validation and detection

  • Inventory WordPress versions and identify any 5.8 beta 1 or beta 2 deployments.
  • Confirm affected beta deployments were upgraded to WordPress 5.8 stable or later.
  • Review Custom HTML widget entries changed during the beta window.
  • Check user accounts able to edit widgets during the affected period.
  • Look for unexpected widget content changes or suspicious administrative activity.
Prepared
Confidence
high
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-79: 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
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration 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-2021-39202 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
7.6 (3.1)
Known Exploited
No
Published

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

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

Vulnerability scoring details

Base CVSS 3.1 score

7.6High
CVSS 3.1 vector shape for CVE-2021-39202Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
WordPresswordpress-develop5.8 beta 1, 5.8 beta 2Listed
Weakness

CWE details

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

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.