Skip to main content
Vulnerability Database/CVE-2026-97315

CVE-2026-97315: Responsive Blocks WordPress XSS Vulnerability

CVE-2026-97315 is a cross-site scripting flaw in Responsive Blocks WordPress plugin that lets attackers inject malicious HTML into notification emails. This post covers technical details, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-97315 Overview

CVE-2026-97315 affects the Responsive Blocks WordPress plugin in versions prior to 2.3.0. The plugin fails to sanitize or escape values submitted through its Form block before embedding them in the HTML notification email sent to the site owner. Unauthenticated attackers can inject arbitrary HTML, including phishing links, into that email. The flaw is categorized under [CWE-74] as an improper neutralization of special elements in output used by a downstream component.

Critical Impact

Unauthenticated attackers can inject phishing content directly into administrator notification emails, enabling targeted social engineering against site owners.

Affected Products

  • Responsive Blocks WordPress plugin versions before 2.3.0
  • WordPress sites exposing the Responsive Blocks Form block
  • Site administrators who receive form submission email notifications

Discovery Timeline

  • 2026-10-14 - CVE-2026-97315 published to NVD
  • 2026-10-14 - Last updated in NVD database

Technical Details for CVE-2026-97315

Vulnerability Analysis

The Responsive Blocks plugin provides a Form block that captures user input and forwards it to the site owner via an HTML email. The plugin inserts submitted field values into the email body without applying HTML escaping or sanitization. An unauthenticated visitor can supply crafted input containing HTML tags, including anchor elements, <img> tags, or styled content. The resulting email renders attacker-controlled markup in the site owner's inbox.

Because the output context is an HTML email client, the attack succeeds without executing JavaScript on the WordPress site itself. The vulnerability enables phishing campaigns that leverage the trust an administrator places in notifications from their own website. Attackers can impersonate internal workflows, request credential resets, or direct recipients to credential-harvesting pages.

Root Cause

The root cause is missing output encoding when assembling the HTML notification email. The plugin treats user-supplied form values as safe text and concatenates them into HTML without calling WordPress sanitization helpers such as wp_kses() or esc_html(). This is a classic injection flaw mapped to [CWE-74].

Attack Vector

Exploitation requires only network access to a page that renders the vulnerable Form block. An attacker submits a form with field values containing HTML payloads. The site owner, upon opening the resulting notification email, sees injected content rendered by their mail client. User interaction is limited to the administrator reading the email, which aligns with the UI:R component of the published CVSS vector.

See the WPScan Vulnerability Report for technical details.

Detection Methods for CVE-2026-97315

Indicators of Compromise

  • Notification emails from the WordPress site containing anchor tags, external image references, or styled HTML in form field values
  • Form submissions where visible field content includes <a href>, <img src>, or inline CSS attributes
  • Administrator reports of phishing links appearing to originate from the site's own form notifications

Detection Strategies

  • Inspect outbound mail logs for notification messages whose body contains HTML tags inside captured form fields
  • Review the WordPress plugin inventory for Responsive Blocks installations below version 2.3.0
  • Correlate form submission records with mail server logs to identify crafted inputs targeting administrator inboxes

Monitoring Recommendations

  • Enable logging on the WordPress site for all Form block submissions, including source IP and submitted payloads
  • Configure the mail gateway to flag outbound messages containing suspicious anchor hrefs or newly registered external domains
  • Monitor administrator mailbox rules and reported-phishing queues for messages originating from the WordPress notification sender

How to Mitigate CVE-2026-97315

Immediate Actions Required

  • Update the Responsive Blocks plugin to version 2.3.0 or later on all WordPress sites
  • Audit recent form submission notifications for injected HTML and notify affected administrators
  • Instruct site owners to treat links in form notification emails with caution until patching is confirmed

Patch Information

The vendor addressed the issue in Responsive Blocks version 2.3.0 by sanitizing form field values before inclusion in the HTML notification email. Apply the update through the WordPress plugin dashboard or by deploying the latest release package. Consult the WPScan Vulnerability Report for advisory details.

Workarounds

  • Disable the Responsive Blocks Form block on public pages until the plugin is updated
  • Replace the affected form with an alternative WordPress form plugin that properly escapes HTML in notifications
  • Configure the site mail transport to send notifications as plain text, which prevents HTML rendering of injected markup
bash
# Update Responsive Blocks via WP-CLI
wp plugin update responsive-block-editor-addons --version=2.3.0
wp plugin list --name=responsive-block-editor-addons --fields=name,version,status

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.