CVE-2026-24564

4.3 MEDIUM

📋 TL;DR

This CVE describes a cross-site scripting (XSS) vulnerability in the Textmetrics WordPress plugin that allows attackers to inject malicious scripts into web pages. The vulnerability affects all WordPress sites running Textmetrics plugin versions up to and including 3.6.3. Attackers can execute arbitrary JavaScript in victims' browsers when they visit compromised pages.

💻 Affected Systems

Products:
  • Textmetrics WordPress Plugin (webtexttool)
Versions: All versions up to and including 3.6.3
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Affects WordPress installations with the Textmetrics plugin active. No special configuration required.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

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

🟠

Likely Case

Attackers inject malicious scripts to steal user session data or credentials, potentially leading to account compromise.

🟢

If Mitigated

With proper input validation and output encoding, the impact is limited to minor content manipulation without significant security consequences.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

XSS vulnerabilities are commonly exploited and weaponization is likely given the public disclosure and WordPress plugin popularity.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Version 3.6.4 or later

Vendor Advisory: https://patchstack.com/database/Wordpress/Plugin/webtexttool/vulnerability/wordpress-textmetrics-plugin-3-6-3-arbitrary-shortcode-execution-vulnerability?_s_id=cve

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins → Installed Plugins. 3. Find Textmetrics plugin. 4. Click 'Update Now' if update available. 5. Alternatively, download latest version from WordPress repository and replace plugin files.

🔧 Temporary Workarounds

Disable Plugin

all

Temporarily disable the Textmetrics plugin until patched

wp plugin deactivate webtexttool

Content Security Policy

all

Implement CSP headers to restrict script execution

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

🧯 If You Can't Patch

  • Implement Web Application Firewall (WAF) rules to block XSS payloads
  • Disable user input fields that accept HTML/shortcodes in Textmetrics configuration

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin → Plugins → Installed Plugins for Textmetrics version. If version is 3.6.3 or lower, system is vulnerable.

Check Version:

wp plugin get webtexttool --field=version

Verify Fix Applied:

Verify Textmetrics plugin version is 3.6.4 or higher in WordPress admin panel.

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests containing script tags or JavaScript payloads to Textmetrics endpoints
  • Multiple failed attempts to access Textmetrics admin functions

Network Indicators:

  • HTTP requests with suspicious parameters containing <script> tags or JavaScript code
  • Unexpected outbound connections from WordPress server after Textmetrics requests

SIEM Query:

source="wordpress.log" AND ("webtexttool" OR "textmetrics") AND ("<script>" OR "javascript:" OR "onerror=" OR "onload=")

🔗 References

📤 Share & Export