CVE-2026-2826 | stellarwp Kadence Blocks Plugin up to 3.6.3 on WordPress REST API Endpoint process_pattern upload_files authorization

VDB-355307 · CVE-2026-2826 · EUVD-2026-18985 STELLARWP KADENCE BLOCKS PLUGIN UP TO 3.6.3 ON WORDPRESS REST API ENDPOINT PROCESS_PATTERN UPLOAD_FILES AUTHORIZATION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 5.2 $0-$5k 0.56+ Summaryinfo A vulnerability, which was classified as critical, has been found in stellarwp Kadence Blocks Plugin up to 3.6.3 on WordPress. The impacted element is the function upload_files of the file process_pattern of the component REST API Endpoint. The manipulation leads to authorization. This vulnerability is uniquely identified as CVE-2026-2826. The attack is possible to be carried out remotely. No exploit exists. It is advisable to upgrade the affected component. Detailsinfo A vulnerability was found in stellarwp Kadence Blocks Plugin up to 3.6.3 on WordPress and classified as critical. This issue affects the function upload_files of the file process_pattern of the component REST API Endpoint. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. Impacted is confidentiality, integrity, and availability. The summary by CVE is: 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.6.3. This is due to the plugin not properly verifying that a user has the `upload_files` capability in the `process_pattern` REST API endpoint. This makes it possible for authenticated attackers, with contributor level access and above, to upload images to the WordPress Media Library by supplying remote image URLs that the server downloads and creates as media attachments. The weakness was disclosed by Lukasz Sobanski. It is possible to read the advisory at wordfence.com. The identification of this vulnerability is CVE-2026-2826 since 02/19/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details of the vulnerability are known, but there is no available exploit. Upgrading to version 3.6.4 eliminates this vulnerability. The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-18985). Productinfo Type WordPress Plugin Vendor stellarwp Name Kadence Blocks Plugin Version 3.6.0 3.6.1 3.6.2 3.6.3 CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 5.3 VulDB Meta Temp Score: 5.2 VulDB Base Score: 6.3 VulDB Temp Score: 6.0 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 4.3 CNA Vector (Wordfence): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Authorization CWE: CWE-862 / CWE-863 / CWE-285 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: Kadence Blocks Plugin 3.6.4 Timelineinfo 02/19/2026 CVE reserved 04/04/2026 +43 days Advisory disclosed 04/04/2026 +0 days VulDB entry created 04/04/2026 +0 days VulDB entry last update Sourcesinfo Advisory: wordfence.com Researcher: Lukasz Sobanski Status: Confirmed CVE: CVE-2026-2826 (🔒) GCVE (CVE): GCVE-0-2026-2826 GCVE (VulDB): GCVE-100-355307 EUVD: 🔒 Entryinfo Created: 04/04/2026 12:11 Updated: 04/04/2026 13:56 Changes: 04/04/2026 12:11 (68), 04/04/2026 13:56 (1) Complete: 🔍 Cache ID: 99:CB1:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸