wpbeaveraddons CVE Vulnerabilities & Metrics

Focus on wpbeaveraddons vulnerabilities and metrics.

Last updated: 08 Mar 2025, 23:25 UTC

About wpbeaveraddons Security Exposure

This page consolidates all known Common Vulnerabilities and Exposures (CVEs) associated with wpbeaveraddons. We track both calendar-based metrics (using fixed periods) and rolling metrics (using gliding windows) to give you a comprehensive view of security trends and risk evolution. Use these insights to assess risk and plan your patching strategy.

For a broader perspective on cybersecurity threats, explore the comprehensive list of CVEs by vendor and product. Stay updated on critical vulnerabilities affecting major software and hardware providers.

Global CVE Overview

Total wpbeaveraddons CVEs: 6
Earliest CVE date: 14 Feb 2022, 12:15 UTC
Latest CVE date: 29 Aug 2024, 11:15 UTC

Latest CVE reference: CVE-2024-7895

Rolling Stats

30-day Count (Rolling): 0
365-day Count (Rolling): 5

Calendar-based Variation

Calendar-based Variation compares a fixed calendar period (e.g., this month versus the same month last year), while Rolling Growth Rate uses a continuous window (e.g., last 30 days versus the previous 30 days) to capture trends independent of calendar boundaries.

Variations & Growth

Month Variation (Calendar): 0%
Year Variation (Calendar): 0%

Month Growth Rate (30-day Rolling): 0.0%
Year Growth Rate (365-day Rolling): 0.0%

Monthly CVE Trends (current vs previous Year)

Annual CVE Trends (Last 20 Years)

Critical wpbeaveraddons CVEs (CVSS ≥ 9) Over 20 Years

CVSS Stats

Average CVSS: 0.72

Max CVSS: 4.3

Critical CVEs (≥9): 0

CVSS Range vs. Count

Range Count
0.0-3.9 5
4.0-6.9 1
7.0-8.9 0
9.0-10.0 0

CVSS Distribution Chart

Top 5 Highest CVSS wpbeaveraddons CVEs

These are the five CVEs with the highest CVSS scores for wpbeaveraddons, sorted by severity first and recency.

All CVEs for wpbeaveraddons

CVE-2024-7895 wpbeaveraddons vulnerability CVSS: 0 29 Aug 2024, 11:15 UTC

The Beaver Builder – WordPress Page Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘type’ parameter in all versions up to, and including, 2.8.3.5 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

CVE-2024-43330 wpbeaveraddons vulnerability CVSS: 0 18 Aug 2024, 14:15 UTC

Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in IdeaBox Creations PowerPack for Beaver Builder allows Reflected XSS.This issue affects PowerPack for Beaver Builder: from n/a before 2.37.4.

CVE-2024-37409 wpbeaveraddons vulnerability CVSS: 0 22 Jul 2024, 09:15 UTC

Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Beaver Addons PowerPack Lite for Beaver Builder allows Stored XSS.This issue affects PowerPack Lite for Beaver Builder: from n/a through 1.3.0.4.

CVE-2024-37410 wpbeaveraddons vulnerability CVSS: 0 09 Jul 2024, 11:15 UTC

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Beaver Addons PowerPack Lite for Beaver Builder allows Path Traversal.This issue affects PowerPack Lite for Beaver Builder: from n/a through 1.3.0.3.

CVE-2024-2289 wpbeaveraddons vulnerability CVSS: 0 09 Apr 2024, 19:15 UTC

The PowerPack Lite for Beaver Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the link in multiple elements in all versions up to, and including, 1.3.0 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

CVE-2022-0176 wpbeaveraddons vulnerability CVSS: 4.3 14 Feb 2022, 12:15 UTC

The PowerPack Lite for Beaver Builder WordPress plugin before 1.2.9.3 does not sanitise and escape the tab parameter before outputting it back in an admin page, leading to a Reflected Cross-Site Scripting