CVE-2026-24564
BaseFortify
Publication date: 2026-01-23
Last updated on: 2026-04-28
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| textmetrics | webtexttool | From 3.0.0 (inc) to 3.6.3 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-80 | The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not specify how this vulnerability affects compliance with common standards and regulations such as GDPR or HIPAA.
Can you explain this vulnerability to me?
CVE-2026-24564 is a content injection vulnerability in the WordPress Textmetrics plugin (up to version 3.6.3) that allows a malicious actor to inject arbitrary content, such as script-related HTML tags, into website pages and posts. This is a type of Cross-Site Scripting (XSS) vulnerability where improper neutralization of script-related HTML tags enables code injection. Exploitation requires only subscriber-level privileges or developer access. [1]
How can this vulnerability impact me? :
This vulnerability can allow attackers to inject unauthorized content into your website, potentially including phishing pages or malicious scripts. This can lead to compromised website integrity, user trust issues, and possible exploitation of site visitors through malicious code execution. Although the severity is rated low (CVSS 4.3), it still poses a risk of unauthorized content manipulation on affected WordPress sites. [1]
What immediate steps should I take to mitigate this vulnerability?
Since no official fix or patched version is currently available for this vulnerability, immediate mitigation steps include restricting subscriber-level and developer access to trusted users only, monitoring website content for unauthorized changes or injections, and applying strict input validation and sanitization where possible to reduce the risk of content injection. [1]