Kadence Blocks — Page Builder Toolkit For Gutenberg Editor
Approved changes feed: RSS · Atom
cpe:2.3:a:stellarwp:kadence_blocks_—_page_builder_toolkit_for_gutenberg_editor:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Stellarwp (85cedc32-4162-5fac-82cb-4647b1b8e38d) |
|---|---|
| Product | Kadence Blocks — Page Builder Toolkit For Gutenberg Editor (16ab4845-b5ec-5e95-8d0d-75c79913c5ef) |
| 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-18062 |
vulnerable | 2026-09-16 04:34:01.816202 |
Kadence Blocks <= 3.7.8.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via Identity Block Inner Image Content
MEDIUM (6.4)
The Kadence Blocks — Page Builder Toolkit for Gutenberg Editor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Identity Block Inner Image Content in all versions up to, and including, 3.7.8.1 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. This vulnerability is only triggerable when the block's urlTransparent attribute is set to a non-empty value, as this is a required precondition for the vulnerable code path in build_html() to be reached.
Published: 2026-08-01T07:49:47.952Z
Updated: 2026-08-03T15:38:36.792Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-18435 |
vulnerable | 2026-09-16 04:34:01.570567 |
Kadence Blocks <= 3.7.8 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'toggleIcon' Block Attribute
MEDIUM (6.4)
The Kadence Blocks — Page Builder Toolkit for Gutenberg Editor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'toggleIcon' Block Attribute in all versions up to, and including, 3.7.8 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.
Published: 2026-08-01T07:49:47.486Z
Updated: 2026-08-03T17:35:46.899Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-15286 |
vulnerable | 2026-07-29 00:26:17.947998 |
Gutenberg Blocks with AI by Kadence WP – Page Builder Features <= 3.5.32 - Incorrect Authorization to Authenticated (Contributor+) Post Publication
MEDIUM (4.3)
The Gutenberg Blocks with AI by Kadence WP – Page Builder Features plugin for WordPress is vulnerable to unauthorized post publication in all versions up to, and including, 3.5.32 due to a misconfigured capability check on the 'get_items_permission_check' function permission callback of the 'process_pattern' REST API endpoint. This makes it possible for authenticated attackers, with Contributor-level access and above, to create and immediately publish posts of any type (including pages), bypassing the standard WordPress review workflow where contributors must submit posts for administrator approval.
Published: 2026-07-10T04:31:22.171Z
Updated: 2026-07-10T15:24:11.323Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-12904 |
vulnerable | 2026-07-29 00:23:32.673044 |
Kadence Blocks <= 3.7.7 - Insecure Direct Object Reference to Authenticated (Contributor+) Arbitrary Optimizer Data Deletion/Read/Modification via 'post_path' Parameter
MEDIUM (4.3)
The Kadence Blocks – Gutenberg Blocks for Page Builder Features plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to and including 3.7.7. This is due to a mismatch between the object used for authorization and the object actually accessed in the Optimize_Rest_Controller's create_item(), get_item(), delete_item(), and bulk_delete_items() endpoints — authorization is checked via current_user_can('edit_post'/'delete_post', $post_id) against the user-supplied post_id, while the storage layer keys analysis records on sha256($post_path) from a separately supplied, attacker-controlled post_path parameter, with no enforcement that post_path corresponds to post_id. This makes it possible for authenticated attackers, with Contributor-level access and above, to read or delete optimizer analysis records belonging to posts owned by other users by submitting their own post_id (which passes the capability check) together with the victim post's path.
Published: 2026-07-01T03:43:34.639Z
Updated: 2026-07-01T10:42:11.715Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-12902 |
vulnerable | 2026-07-29 00:23:32.672732 |
Kadence Blocks <= 3.7.7 - Missing Authorization to Authenticated (Contributor+) Arbitrary Media Attachment Creation via kadence_import_process_pattern/kadence_import_process_data AJAX Actions
MEDIUM (4.3)
The Kadence Blocks — Page Builder Toolkit for Gutenberg Editor plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 3.7.7. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with contributor-level access and above, to create arbitrary Media Library attachments by downloading remote images to the site's uploads directory via wp_upload_bits() and wp_insert_attachment(), bypassing the upload_files capability boundary.
Published: 2026-07-01T03:43:36.478Z
Updated: 2026-07-01T10:32:05.956Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-11357 |
vulnerable | 2026-07-29 00:23:30.960720 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-2826 |
vulnerable | 2026-06-08 07:55:17.576396 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-2633 |
vulnerable | 2026-06-08 07:55:17.313400 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-2608 |
vulnerable | 2026-06-08 07:55:17.288771 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-1857 |
vulnerable | 2026-06-08 07:49:09.760708 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-5678 |
vulnerable | 2026-06-08 07:37:25.440730 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-1291 |
vulnerable | 2026-06-08 07:08:36.260899 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-9655 |
vulnerable | 2026-06-08 07:00:28.405466 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-5819 |
vulnerable | 2026-06-08 06:56:17.500083 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-5289 |
vulnerable | 2026-06-08 06:56:15.424401 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-4863 |
vulnerable | 2026-06-08 06:50:18.814348 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-4481 |
vulnerable | 2026-06-08 06:50:17.839921 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-4209 |
vulnerable | 2026-06-08 06:50:17.226851 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-4208 |
vulnerable | 2026-06-08 06:50:17.226319 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-3189 |
vulnerable | 2026-06-08 06:41:52.663738 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-2919 |
vulnerable | 2026-06-08 06:35:27.703545 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-2273 |
vulnerable | 2026-06-08 06:33:30.742676 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-1999 |
vulnerable | 2026-06-08 06:27:15.216295 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-1541 |
vulnerable | 2026-06-08 06:27:13.323002 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-12581 |
vulnerable | 2026-06-08 06:25:35.584557 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-12304 |
vulnerable | 2026-06-08 06:23:51.692563 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-10785 |
vulnerable | 2026-06-08 06:23:47.542592 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-0598 |
vulnerable | 2026-06-08 06:22:01.456627 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-6964 |
vulnerable | 2026-06-08 06:21:56.488490 | 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.