CVE-2026-24576
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 |
|---|---|---|
| patchstack | ux_flat | From 5.4.0|end_including=5.4.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-24576 is a Stored Cross Site Scripting (XSS) vulnerability in the WordPress UX Flat Plugin versions up to and including 5.4.0. It allows an attacker to inject malicious scripts into web pages generated by the plugin. Exploitation requires a privileged user (Contributor or Developer) to interact with crafted content, such as clicking a malicious link or submitting a form. Once exploited, the malicious scripts execute when site visitors access the compromised pages, potentially causing redirects, displaying unwanted advertisements, or other harmful HTML payloads. [1]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to execute malicious scripts on your website through the UX Flat Plugin. This can lead to unauthorized redirects, display of unwanted advertisements, or other malicious content affecting your site visitors. However, exploitation requires interaction by a privileged user, which limits the risk. The overall severity is moderate with a CVSS score of 6.5, and there is currently no official fix available. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves monitoring for suspicious input or script injections in the UX Flat plugin pages, especially actions performed by users with Contributor or Developer roles. Since exploitation requires user interaction with crafted pages or forms, reviewing logs for unusual POST requests or script payloads in input fields can help. Specific commands are not provided in the resources, but general approaches include using web application scanners to detect stored XSS or inspecting HTTP requests and responses for injected scripts. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting privileged user roles (Contributor or Developer) from interacting with untrusted content or links, educating users about the risk of clicking unknown links, and monitoring for suspicious activity. Since no official fix or patched version is available, applying strict input validation and output encoding where possible, and limiting user permissions can reduce risk. [1]