cve.bz

CVE-2026-93485 automattic wordpress: Cross-site Scripting

7.1 highEPSS 0.8%Fix available

High (7.1) in automattic wordpress. EPSS 0.8% estimated probability of exploitation activity in the next 30 days.

On this page
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Automattic WordPress wordpress allows DOM-Based XSS.This issue affects WordPress: from n/a through 7.1.

Severity

CVSS 3.1

7.1 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
EPSS
0.8% (unchanged from 0.8% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 56th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-09-19. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-79 Improper Neutralization of Input During Web Page Generation (Cross-site Scripting)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • Automattic WordPress: fixed in 7.0.5
  • Automattic WordPress: fixed in 6.9.8
  • Automattic WordPress: fixed in 6.8.9
  • Automattic WordPress: fixed in 6.7.8
  • Automattic WordPress: fixed in 6.6.8
  • Automattic WordPress: fixed in 6.5.11
  • Automattic WordPress: fixed in 6.4.11
  • Automattic WordPress: fixed in 6.3.11
  • Debian: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-93485 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-93485?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-93485?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-93485 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Automattic WordPress7.1
Automattic WordPressfrom 7.0 through 7.0.4
Automattic WordPressfrom 6.9 through 6.9.7
Automattic WordPressfrom 6.8 through 6.8.8
Automattic WordPressfrom 6.7 through 6.7.7
Automattic WordPressfrom 6.6 through 6.6.7
Automattic WordPressfrom 6.5 through 6.5.10
Automattic WordPressfrom 6.4 through 6.4.10
Automattic WordPressfrom 6.3 through 6.3.10
Automattic WordPressfrom 6.2 through 6.2.11
Automattic WordPressfrom 6.1 through 6.1.12
Automattic WordPressfrom 6.0 through 6.0.14
Automattic WordPressfrom 5.9 through 5.9.16
Automattic WordPressfrom 5.8 through 5.8.15
Automattic WordPressfrom 5.7 through 5.7.17
Automattic WordPressfrom 5.6 through 5.6.19
Automattic WordPressfrom 5.5 through 5.5.20
Automattic WordPressfrom 5.4 through 5.4.21
Automattic WordPressfrom 5.3 through 5.3.23
Automattic WordPressfrom 5.2 through 5.2.26
Automattic WordPressfrom 5.1 through 5.1.24
Automattic WordPressfrom 5.0 through 5.0.27
Automattic WordPressfrom 4.9 through 4.9.31
Automattic WordPressfrom 4.8 through 4.8.30
Automattic WordPressfrom 4.7 through 4.7.35

Fixed in

ProductFixed in
Automattic WordPress7.0.5
Automattic WordPress6.9.8
Automattic WordPress6.8.9
Automattic WordPress6.7.8
Automattic WordPress6.6.8
Automattic WordPress6.5.11
Automattic WordPress6.4.11
Automattic WordPress6.3.11
Automattic WordPress6.2.12
Automattic WordPress6.1.13
Automattic WordPress6.0.15
Automattic WordPress5.9.17
Automattic WordPress5.8.16
Automattic WordPress5.7.18
Automattic WordPress5.6.20
Automattic WordPress5.5.21
Automattic WordPress5.4.22
Automattic WordPress5.3.24
Automattic WordPress5.2.27
Automattic WordPress5.1.25
Automattic WordPress5.0.28
Automattic WordPress4.9.32
Automattic WordPress4.8.31
Automattic WordPress4.7.36

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12wordpressno fix listedDEBIAN-CVE-2026-93485
Debian13wordpress6.8.10+dfsg1-0+deb13u1DEBIAN-CVE-2026-93485
Debian14wordpress7.1.1+dfsg1-1DEBIAN-CVE-2026-93485
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 morewordpressno fix listedUBUNTU-CVE-2026-93485

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • DeathShotXD/Comment2Shell Harbor Check: matches CVE 71 stars, created
    Comment2Shell is a zero click pre auth RCE exploit for WordPress CVE-2026-93485. An anonymous comment plants stored XSS that fires when an …
  • 686f6c61/POC-WP-CORE-CVE-2026-93485 Harbor Check: matches CVE 2 stars, Python, created
    Laboratorio pedagógico de CVE-2026-93485 (Comment2Shell): stored XSS no autenticado en WordPress core vía wpautop -> RCE, con demo del root…
  • ashrafzaryouh/CVE-2026-93485 0 stars, Python, created
    CVE-2026-93485
  • HORKimhab/CVE-2026-93485 0 stars, created
    CVE-2026-93485 - Draft or TODO

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

  • CAPEC-63 Cross-Site Scripting (XSS) Likelihood: High · Severity: Very High
  • CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
  • CAPEC-209 XSS Using MIME Type Mismatch Severity: Medium
  • CAPEC-588 DOM-Based XSS Likelihood: High · Severity: Very High
  • CAPEC-591 Reflected XSS Likelihood: High · Severity: Very High
  • CAPEC-592 Stored XSS Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON