CVE-2026-97315 Responsive Blocks CVE debrief

Who should care

Site administrators and security teams responsible for WordPress installations using the Responsive Blocks plugin should assess their exposure and take necessary actions to protect their sites.

Why it matters

CVE-2026-97315 is a MEDIUM-severity vulnerability in the Responsive Blocks WordPress plugin that allows unauthenticated HTML injection in form notification emails. Site administrators and security teams should verify their exposure, apply necessary updates, and monitor email content to prevent potential phishing attacks and reputation damage.

• Potential phishing attacks through injected HTML in notification emails
• Possible defacement of notification emails
• Required verification of plugin version and email content
• Potential impact on site reputation and user trust

Technical summary

The Responsive Blocks WordPress plugin before version 2.3.0 does not properly sanitize or escape user-submitted values from its Form block before including them in the HTML of notification emails sent to site owners. This allows unauthenticated attackers to inject arbitrary HTML, such as phishing links, into these emails. Site administrators and security teams should verify their exposure, apply necessary updates, and monitor email content to prevent potential phishing attacks and reputation damage. Defenders should prioritize verifying if their site uses a vulnerable version of the Responsive Blocks plugin and apply the necessary updates.

Defensive priority

Defenders should prioritize verifying if their site uses a vulnerable version of the Responsive Blocks plugin and apply the necessary updates. They should also monitor notification emails for suspicious content.

Recommended defensive actions

• Verify if the site uses a vulnerable version of the Responsive Blocks plugin
• Apply necessary updates to the plugin
• Monitor notification emails for suspicious content
• Implement additional security measures for email notifications
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and source item provide details about the vulnerability. However, the corpus does not establish versions beyond 2.3.0, exploitation, impact, or remediation, which require verification from the supplied official sources.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.