CVE-2026-22488
Missing Authorization in Dashboard Welcome for Beaver Builder
Publication date: 2026-01-08
Last updated on: 2026-04-23
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ideabox_creations | dashboard_welcome_for_beaver_builder | From 1.0.0 (inc) to 1.0.8 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-22488 is a broken access control vulnerability in the WordPress plugin 'Dashboard Welcome for Beaver Builder' up to version 1.0.8. It occurs due to missing authorization, authentication, or nonce token checks in certain functions, which allows unauthenticated users to perform actions that normally require higher privileges. [1]
How can this vulnerability impact me? :
This vulnerability allows unauthenticated users to perform privileged actions, potentially leading to unauthorized changes or misuse within the affected plugin. However, the severity is considered low (CVSS 5.3), and exploitation is unlikely. There is no impact on confidentiality or availability, but integrity could be affected. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
There are no specific detection commands or network indicators provided for this vulnerability. Detection would involve reviewing the WordPress plugin 'Dashboard Welcome for Beaver Builder' version installed (up to 1.0.8) for missing authorization or access control issues. Since the vulnerability allows unauthenticated users to perform privileged actions, monitoring for unusual or unauthorized access attempts to plugin functions could help. However, no explicit commands or detection tools are mentioned. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include monitoring for unauthorized access attempts and applying general security best practices, such as restricting access to the plugin or disabling it if not essential. Since there is no official fix or patched version available as of the publication date, applying security hardening measures and keeping the plugin updated when a patch is released are recommended. [1]