CVE-2026-30689 | blog.admin up to 8.0 API Interface getinfobytoken access control

VDB-353914 · CVE-2026-30689 · GCVE-0-2026-30689 BLOG.ADMIN UP TO 8.0 API INTERFACE GETINFOBYTOKEN ACCESS CONTROL HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 4.3 $0-$5k 1.09+ Summaryinfo A vulnerability categorized as problematic has been discovered in blog.admin up to 8.0. Affected by this vulnerability is the function getinfobytoken of the component API Interface. Executing a manipulation can lead to access control. The identification of this vulnerability is CVE-2026-30689. The attack may be launched remotely. There is no exploit available. Detailsinfo A vulnerability was found in blog.admin up to 8.0. It has been declared as problematic. This vulnerability affects the function getinfobytoken of the component API Interface. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. As an impact it is known to affect confidentiality. CVE summarizes: A blog.admin v.8.0 and before system's getinfobytoken API interface contains an improper access control which leads to sensitive data exposure. Unauthorized parties can obtain sensitive administrator account information via a valid token, threatening system security. This vulnerability was named CVE-2026-30689 since 03/04/2026. The exploitation appears to be easy. The attack can be initiated remotely. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 03/27/2026). This vulnerability is assigned to T1068 by the MITRE ATT&CK project. There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product. Productinfo Name blog.admin Version 8.0 CPE 2.3info 🔒 CPE 2.2info 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 4.3 VulDB Meta Temp Score: 4.3 VulDB Base Score: 4.3 VulDB Temp Score: 4.3 VulDB Vector: 🔒 VulDB Reliability: 🔍 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: Access control CWE: CWE-284 / CWE-266 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: no mitigation known Status: 🔍 0-Day Time: 🔒 Timelineinfo 03/04/2026 CVE reserved 03/27/2026 +23 days Advisory disclosed 03/27/2026 +0 days VulDB entry created 03/27/2026 +0 days VulDB entry last update Sourcesinfo Status: Not defined CVE: CVE-2026-30689 (🔒) GCVE (CVE): GCVE-0-2026-30689 GCVE (VulDB): GCVE-100-353914 Entryinfo Created: 03/27/2026 15:44 Changes: 03/27/2026 15:44 (52) Complete: 🔍 Cache ID: 99:BAB:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸