HomeIntelligenceBrief
VULNERABILITY BRIEF 🟠 High Vulnerability

WordPress ‘Comment2Shell’ (CVE‑2026‑93485) Lets Anonymous Comment Lead to Remote Code Execution via Admin Session

A newly disclosed WordPress core flaw (CVE‑2026‑93485) enables an anonymous comment to inject a script that runs as the logged‑in administrator, achieving remote code execution. The issue underscores the importance of rapid patching, robust admin session controls, and continuous control mapping for audit readiness.

Verisq™ Intelligence · 📅 September 22, 2026 · 📰 thehackernews.com
🟠
Severity
High
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
1 sector(s)
Actions
4 recommended
📰
Source
thehackernews.com

WordPress “Comment2Shell” (CVE‑2026‑93485) Enables Anonymous XSS to RCE via Admin Session

What It Is — A newly disclosed WordPress core flaw (CVE‑2026‑93485) lets an anonymous visitor post a comment that injects a hidden script. When a logged‑in administrator later views the page, the script runs in the admin’s session and can execute arbitrary code on the web server.

Exploitability — The vulnerability is publicly disclosed and a proof‑of‑concept exists; an attacker only needs to submit a crafted comment and wait for an admin to view the page. CVSS is estimated at 8.5 (High).

Affected Products — WordPress core versions prior to 7.1.1 (all installations that allow unauthenticated commenting).

Why It Matters for Trust & Control Assurance

  • Demonstrates the need for continuous patch management evidence – organizations must prove they apply critical updates promptly to maintain a defensible audit trail.
  • Highlights gaps in access‑control and session‑management controls – admin sessions should be tightly governed and monitored to prevent privilege misuse.
  • Reinforces the value of continuous control mapping – mapping this vulnerability to the “Identity & Access Management” control area shows compliance posture across multiple frameworks (e.g., NIST CSF 2.0).

Recommended Actions

  1. Upgrade all WordPress installations to version 7.1.1 or later immediately.
  2. Enforce least‑privilege for admin accounts and consider multi‑factor authentication for all privileged users.
  3. Deploy a Web Application Firewall (WAF) that blocks suspicious script injections in comment fields.
  4. Capture patch‑deployment evidence and update your control‑mapping repository to reflect remediation of the access‑control gap.

Source: The Hacker News

📰 Original Source
https://thehackernews.com/2026/09/wordpress-comment2shell-flaw-can-turn.html

This Verisq Intelligence Brief is an independent analysis. Read the original reporting at the link above.

Vulnerability exposure

Is this CVE in your supply chain?

Verisq matches published vulnerabilities against the software your vendors run, so you know which relationships this touches before the next review.

See vendor exposure →