CVE-2025-32198

6.5 MEDIUM

📋 TL;DR

This is a cross-site scripting (XSS) vulnerability in the Brizy WordPress plugin that allows attackers to inject malicious scripts into web pages. It affects all Brizy plugin versions up to 2.6.14, potentially compromising WordPress sites using this plugin.

💻 Affected Systems

Products:
  • Brizy WordPress plugin
Versions: All versions up to and including 2.6.14
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects WordPress installations with Brizy plugin enabled.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal session cookies, redirect users to malicious sites, deface websites, or perform actions on behalf of authenticated users.

🟠

Likely Case

Attackers inject malicious JavaScript to steal user session cookies or credentials, potentially gaining administrative access to WordPress sites.

🟢

If Mitigated

With proper input validation and output encoding, malicious scripts would be neutralized before reaching users.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

XSS vulnerabilities typically have low exploitation complexity and can be exploited without authentication.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 2.6.15 or later

Vendor Advisory: https://patchstack.com/database/wordpress/plugin/brizy/vulnerability/wordpress-brizy-plugin-2-6-14-cross-site-scripting-xss-vulnerability?_s_id=cve

Restart Required: No

Instructions:

1. Log into WordPress admin panel
2. Navigate to Plugins > Installed Plugins
3. Find Brizy plugin
4. Click 'Update Now' if available
5. Alternatively, download latest version from WordPress repository

🔧 Temporary Workarounds

Disable Brizy plugin

all

Temporarily disable the Brizy plugin until patched

wp plugin deactivate brizy

Implement Content Security Policy

all

Add CSP headers to restrict script execution

Add to .htaccess: Header set Content-Security-Policy "default-src 'self'"
Add to nginx config: add_header Content-Security-Policy "default-src 'self'";

🧯 If You Can't Patch

  • Implement web application firewall (WAF) rules to block XSS payloads
  • Enable WordPress security plugins with XSS protection features

🔍 How to Verify

Check if Vulnerable:

Check Brizy plugin version in WordPress admin panel under Plugins > Installed Plugins

Check Version:

wp plugin get brizy --field=version

Verify Fix Applied:

Verify Brizy plugin version is 2.6.15 or higher after update

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests containing script tags or JavaScript code
  • Multiple failed XSS attempts in web server logs

Network Indicators:

  • HTTP requests with suspicious parameters containing script tags or JavaScript

SIEM Query:

source="web_server" AND ("<script" OR "javascript:" OR "onload=" OR "onerror=")

🔗 References

📤 Share & Export