CVE-2026-12904: Kadence Blocks <= 3.7.7 - Insecure Direct Object Reference to Authenticated (Contributor+) Arbitrary Optimizer Data Deletion/Read/Modification via 'post_path' Parameter
stellarwp · Kadence Blocks — Page Builder Toolkit for Gutenberg Editor
Affected: stellarwp Kadence Blocks — Page Builder Toolkit for Gutenberg Editor · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 39% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- stellarwp · Kadence Blocks — Page Builder Toolkit for Gutenberg Editorup to and including 3.7.7
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Weakness
- Insecure Direct Object Reference
- Vendor
- stellarwp
- Published
- July 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-12904 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.
References
- NVD entrynvd.nist.gov
- CVE recordcve.org
- Weakness CWE-639cwe.mitre.org
- wordfence.com/threat-intel/vulnerabilities/id/24cdd50f-742c-457cwordfence.com
- plugins.trac.wordpress.org/browser/kadence-blocks/tags/3.7.6/incplugins.trac.wordpress.org
- plugins.trac.wordpress.org/browser/kadence-blocks/tags/3.7.6/incplugins.trac.wordpress.org
- plugins.trac.wordpress.org/browser/kadence-blocks/tags/3.7.6/incplugins.trac.wordpress.org
- plugins.trac.wordpress.org/browser/kadence-blocks/tags/3.7.6/incplugins.trac.wordpress.org
- plugins.trac.wordpress.org/browser/kadence-blocks/tags/3.7.6/incplugins.trac.wordpress.org
- plugins.trac.wordpress.org/browser/kadence-blocks/tags/3.7.6/incplugins.trac.wordpress.org
- plugins.trac.wordpress.org/browser/kadence-blocks/tags/3.7.6/incplugins.trac.wordpress.org
- plugins.trac.wordpress.org/browser/kadence-blocks/tags/3.7.6/incplugins.trac.wordpress.org
- plugins.trac.wordpress.org/browser/kadence-blocks/tags/3.7.6/incplugins.trac.wordpress.org
- plugins.trac.wordpress.org/browser/kadence-blocks/tags/3.6.7/incplugins.trac.wordpress.org
- plugins.trac.wordpress.org/browser/kadence-blocks/tags/3.6.7/incplugins.trac.wordpress.org
8 more references are in the CVE record.