DOM-Based Cross-Site Scripting in WordPress Core

Improper neutralization of input during web page generation ('cross-site scripting') vulnerability in Automattic WordPress core allows DOM-Based XSS. This issue affects WordPress versions 7.1 before 7.1.1; 7.0 through 7.0.4; 6.9 through 6.9.7; 6.8 through 6.8.8; 6.7 through 6.7.7; 6.6 through 6.6.7; 6.5 through 6.5.10; 6.4 through 6.4.10; 6.3 through 6.3.10; 6.2 through 6.2.11; 6.1 through 6.1.12; 6.0 through 6.0.14; 5.9 through 5.9.16; 5.8 through 5.8.15; 5.7 through 5.7.17; 5.6 through 5.6.19; 5.5 through 5.5.20; 5.4 through 5.4.21; 5.3 through 5.3.23; 5.2 through 5.2.26; 5.1 through 5.1.24; 5.0 through 5.0.27; 4.9 through 4.9.31; 4.8 through 4.8.30; and 4.7 through 4.7.35. The Unauthenticated Stored XSS vulnerability in the WordPress core can be reproduced on a default WordPress installation. Comment moderation is disabled by default, and the requirement for commenters to have a previously approved comment can be bypassed.

Casky was already ahead

This CVE exploits attack patterns that Casky's 323matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

This DOM-Based XSS vulnerability (CWE-79) in WordPress core represents a critical threat to the estimated 43% of websites running WordPress globally. The vulnerability stems from improper neutralization of user input during web page generation, allowing attackers to inject malicious scripts that execute in users' browsers. With a CVSS score of 7.1 and affecting versions dating back to 5.6, the attack surface is enormous—spanning nearly a decade of WordPress releases. Attackers can exploit this to steal session cookies, perform actions on behalf of users, redirect traffic, or harvest sensitive information from administrators and site visitors alike.

Casky's 323 matching skills detect the attack patterns mapped to Initial Access (TA0001) and Persistence (TA0043) by analyzing how malicious payloads flow through WordPress sanitization layers. Practitioners using Casky with Claude's extended reasoning would identify findings showing DOM manipulation chains where user-controlled data bypasses input validation, suspicious script injection points in wp-admin contexts, and behavioral signatures of stored XSS persistence mechanisms. The platform would flag specific code paths where JavaScript execution occurs without proper output encoding, trace attack chains from initial injection through DOM mutation, and correlate these patterns with known WordPress plugin interactions that amplify vulnerability exposure—enabling teams to prioritize patching across their entire WordPress fleet systematically.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

323 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-93485.

Abuse of Public-Facing API: Mobile API Abuse

mobile security · low

Run

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

MITRE ATT&CK Techniques

TA0001 TA0043

Investigate the attack patterns behind CVE-2026-93485

Casky has 323 skills that investigate the attack patterns behind CVE-2026-93485. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn