Radar sectionsDatabase
Check my site
WordPress plugin

Kadence Blocks <= 3.7.7 — Insecure Direct Object Reference to Authenticated (Contributor+) Arbitrary Optimizer Data Deletion/Read/Modification via 'post_path' Parameter

CVE-2026-12904Published · Updated

Action summary

Affected: ≤3.7.7Update to 3.7.8 or newer

All remediation steps
Severity
Medium4.3
CVSS
4.3
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:L Privileges required
Low
UI:N User interaction
None
S:U Scope
Unchanged
C:N Confidentiality
None
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-639 Authorization Bypass Through User-Controlled Key
Required access
Unknown
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

Kadence Blocks — Page Builder Toolkit for Gutenberg Editor kadence-blocks

  1. Affected≤ 3.7.7
  2. Patched in3.7.8

Update to 3.7.8 or newer.

You are affected if you run ≤ 3.7.7. Version 3.7.8 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Kadence Blocks — Page Builder Toolkit for Gutenberg Editor.
  • No admin access? Run a passive check of your site. It reads public files only.

What to do

  1. Update to version 3.7.8, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch Kadence Blocks — Page Builder Toolkit for Gutenberg Editor to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to se1en.

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.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in Kadence Blocks — Page Builder Toolkit for Gutenberg Editor

All 43
More vulnerabilities in Kadence Blocks — Page Builder Toolkit for Gutenberg Editor
SeverityVulnerabilityCVEPublished
Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting
≤3.8.0.2Update to 3.8.1
CVE-2026-39742
Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting
≤3.8.0.1Update to 3.8.0.2
CVE-2026-115602
Medium6.4Authenticated (Author+) Stored Cross-Site Scripting via Block Font Family Attribute
≤3.7.12Update to 3.7.12.1
CVE-2026-104762
Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting
≤3.7.12Update to 3.7.12.1
CVE-2026-105890
High7.2Unauthenticated Stored Cross-Site Scripting
≤3.7.11.1Update to 3.7.12
CVE-2026-103354

Timeline

  1. CVE published

    Severity medium, CVSS 4.3

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
CVE® identifiers
[object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?