Brizy – Page Builder
Approved changes feed: RSS · Atom
cpe:2.3:a:themefusecom:brizy_–_page_builder:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Themefusecom (c334df56-9460-553e-bf29-7c42560e360d) |
|---|---|
| Product | Brizy – Page Builder (48a80332-0418-5943-a219-b623ac6e839a) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-5324 |
vulnerable | 2026-06-08 08:07:03.558601 |
Brizy – Page Builder <= 2.8.11 - Unauthenticated Stored Cross-Site Scripting via FileUpload Field Value
HIGH (7.2)
The Brizy – Page Builder plugin for WordPress is vulnerable to Unauthenticated Stored Cross-Site Scripting in all versions up to, and including, 2.8.11 This is due to a combination of missing nonce verification for unauthenticated form submissions, insufficient handling of FileUpload fields when no file is uploaded, and the reversal of security encoding via html_entity_decode() followed by unescaped output in the admin view. The submit_form() function skips nonce verification for non-logged-in users (api.php:198). The handleFileTypeFields() function fails to overwrite user-supplied values when no file is attached. While htmlentities() is applied during storage, html_entity_decode() reverses this on display (form-entries.php:79). The form-data.php template outputs FileUpload values directly in href attributes without esc_url(). This makes it possible for unauthenticated attackers to inject arbitrary web scripts that execute when an administrator views the form Leads page.
Published: 2026-05-02T08:27:05.238Z
Updated: 2026-05-04T17:51:44.700Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-4370 |
vulnerable | 2026-06-08 07:29:16.143483 |
Brizy <= 2.6.20 - Missing Authorization to Unauthenticated Limited File Upload
MEDIUM (5.3)
The Brizy – Page Builder plugin for WordPress is vulnerable to limited file uploads due to missing authorization on process_external_asset_urls function as well as missing path validation in store_file function in all versions up to, and including, 2.6.20. This makes it possible for unauthenticated attackers to upload .TXT files on the affected site's server.
Published: 2025-07-29T04:23:46.517Z
Updated: 2026-04-08T17:27:30.972Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-0969 |
vulnerable | 2026-06-08 07:02:26.073437 |
Brizy – Page Builder <= 2.7.16 - Authenticated (Contributor+) Sensitive Information Exposure via get_users Function
MEDIUM (6.5)
The Brizy – Page Builder plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.7.16 via the get_users() function. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract sensitive data including email addresses and hashed passwords of administrators.
Published: 2025-12-13T08:21:13.768Z
Updated: 2026-04-08T16:54:50.850Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-6254 |
vulnerable | 2026-06-08 06:58:18.405932 |
Brizy – Page Builder <= 2.5.1 - Cross-Site Request Forgery
MEDIUM (4.3)
The Brizy – Page Builder plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.5.1. This is due to missing or incorrect nonce validation on form submissions. This makes it possible for unauthenticated attackers to submit forms intended for public use as another user via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. On sites where unfiltered_html is enabled, this can lead to the admin unknowingly adding a Stored Cross-Site Scripting payload.
Published: 2024-08-08T03:30:45.320Z
Updated: 2026-04-08T17:01:25.787Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-3711 |
vulnerable | 2026-06-08 06:43:51.261566 |
Brizy – Page Builder <= 2.4.43 - Missing Authorization
MEDIUM (4.3)
The Brizy – Page Builder plugin for WordPress is vulnerable to unauthorized plugin setting update due to a missing capability check on the functions action_request_disable, action_change_template, and action_request_enable in all versions up to, and including, 2.4.43. This makes it possible for authenticated attackers, with contributor access or above, to enable/disable the Brizy editor and modify the template used.
Published: 2024-05-23T05:32:15.933Z
Updated: 2026-04-08T17:00:22.356Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-3667 |
vulnerable | 2026-06-08 06:43:51.158867 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-3242 |
vulnerable | 2026-06-08 06:41:52.762489 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-2087 |
vulnerable | 2026-06-08 06:33:30.316007 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-1940 |
vulnerable | 2026-06-08 06:27:15.087173 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-1937 |
vulnerable | 2026-06-08 06:27:15.079373 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-1311 |
vulnerable | 2026-06-08 06:25:39.790479 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-1296 |
vulnerable | 2026-06-08 06:25:39.756059 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-1293 |
vulnerable | 2026-06-08 06:25:39.744413 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-1291 |
vulnerable | 2026-06-08 06:25:39.740675 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-1165 |
vulnerable | 2026-06-08 06:25:39.438015 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-1164 |
vulnerable | 2026-06-08 06:25:39.437225 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-1161 |
vulnerable | 2026-06-08 06:25:39.429236 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-10960 |
vulnerable | 2026-06-08 06:23:48.275293 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-10322 |
vulnerable | 2026-06-08 06:22:04.003080 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-2897 |
vulnerable | 2026-06-08 06:02:43.614511 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-36714 |
vulnerable | 2026-06-08 05:25:49.451840 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.