CVE-2026-4811
Stored XSS in WPB Floating Menu & Categories WordPress Plugin
Publication date: 2026-05-21
Last updated on: 2026-05-21
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wpb | floating_menu_and_categories_for_wordpress | to 1.0.8 (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
How can this vulnerability impact me? :
This vulnerability allows attackers with Editor-level access or above to inject malicious scripts that execute in the context of other users visiting the affected pages.
The impact includes potential compromise of user sessions, theft of sensitive information, or unauthorized actions performed on behalf of users without their consent.
The CVSS score of 4.9 indicates a medium severity with high confidentiality impact but no impact on integrity or availability.
Can you explain this vulnerability to me?
The WPB Floating Menu & Categories for WordPress – Sticky Side Menu with Icons plugin is vulnerable to Stored Cross-Site Scripting (XSS) through the 'Icon CSS Class' category field. This vulnerability exists in all versions up to and including 1.0.8 due to insufficient input sanitization and output escaping.
Authenticated attackers with Editor-level access or higher can inject arbitrary web scripts into pages. These scripts execute whenever a user accesses the injected page, potentially compromising the security of users.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability affects all versions up to and including 1.0.8 of the WPB Floating Menu & Categories for WordPress – Sticky Side Menu with Icons plugin. Immediate mitigation steps include updating the plugin to a version later than 1.0.8 where the vulnerability is fixed.
Additionally, restrict Editor-level access and above to trusted users only, as the vulnerability requires authenticated users with Editor-level permissions to exploit.