Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-863 (授权机制不正确) — Vulnerability Class 1275

1275 vulnerabilities classified as CWE-863 (授权机制不正确). AI Chinese analysis included.

CWE-863, Incorrect Authorization, represents a critical logic flaw where software fails to properly verify an actor’s permissions before granting access to resources or executing actions. Attackers typically exploit this vulnerability by manipulating input parameters, such as altering user IDs or session tokens, to bypass intended access controls and interact with data or functions reserved for privileged users. This often leads to unauthorized data disclosure, modification, or complete system compromise. To prevent such breaches, developers must implement robust, centralized authorization checks that are consistently applied across all application layers. Relying solely on client-side restrictions is insufficient; instead, server-side validation should enforce strict role-based or attribute-based access controls for every request, ensuring that permission verification occurs reliably before any sensitive operation is permitted.

MITRE CWE Description
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Common Consequences (5)
ConfidentialityRead Application Data, Read Files or Directories
An attacker could bypass intended access restrictions to read sensitive data, either by reading the data directly from a data store that is not correctly restricted, or by accessing insufficiently-protected, privileged functionality to read the data.
IntegrityModify Application Data, Modify Files or Directories
An attacker could bypass intended access restrictions to modify sensitive data, either by writing the data directly to a data store that is not correctly restricted, or by accessing insufficiently-protected, privileged functionality to write the data.
Access ControlGain Privileges or Assume Identity, Bypass Protection Mechanism
An attacker could bypass intended access restrictions to gain privileges by modifying or reading critical data directly, or by accessing privileged functionality.
Confidentiality, Integrity, AvailabilityExecute Unauthorized Code or Commands
An attacker could use elevated privileges to execute unauthorized commands or code.
AvailabilityDoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory), DoS: Resource Consumption (Other)
An attacker could gain unauthorized access to resources on the system and excessively consume those resources, leading to a denial of service.
Mitigations (5)
Architecture and DesignDivide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the …
Architecture and DesignEnsure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible…
Architecture and DesignUse a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
Architecture and DesignFor web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page. One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests …
System Configuration, InstallationUse the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.
Examples (1)
The following code could be for a medical records application. It displays a record to already authenticated users, confirming the user's authorization using a value stored in a cookie.
$role = $_COOKIES['role']; if (!$role) { $role = getRole('user'); if ($role) { // save the cookie to send out in future responses setcookie("role", $role, time()+60*60*2); } else{ ShowLoginScreen(); die("\n"); } } if ($role == 'Reader') { DisplayMedicalHistory($_POST['patient_ID']); } else{ die("You are not Authorized to view this record\n"); }
Bad · PHP
CVE IDTitleCVSSSeverityPublished
CVE-2026-32978 OpenClaw < 2026.3.11 - Approval Bypass via Unrecognized Script Runners — OpenClaw 8.0 High2026-03-29
CVE-2026-32972 OpenClaw < 2026.3.11 - Authorization Bypass in Browser Profile Management via browser.request — OpenClaw 7.1 High2026-03-29
CVE-2026-32924 OpenClaw < 2026.3.12 - Authorization Bypass via Misclassified Reaction Events in Feishu — OpenClaw 9.8 Critical2026-03-29
CVE-2026-32923 OpenClaw < 2026.3.11 - Authorization Bypass in Discord Guild Reaction Allowlist Enforcement — OpenClaw 5.4 Medium2026-03-29
CVE-2026-32919 OpenClaw < 2026.3.11 - Unauthorized Session Reset via agent Slash Commands — OpenClaw 6.1 Medium2026-03-29
CVE-2026-32918 OpenClaw < 2026.3.11 - Session Sandbox Escape via session_status Tool — OpenClaw 8.4 High2026-03-29
CVE-2026-32915 OpenClaw < 2026.3.11 - Sandbox Boundary Bypass via Subagent Control Surface — OpenClaw 8.8 High2026-03-29
CVE-2026-32914 OpenClaw < 2026.3.12 - Insufficient Access Control in /config and /debug Endpoints — OpenClaw 8.8 High2026-03-29
CVE-2026-33884 Statamic's live preview token bypasses content protection for unrelated entries — cms 4.3 Medium2026-03-27
CVE-2026-33869 Mastodon has a denial of service for quote authorization — mastodon 4.8 Medium2026-03-27
CVE-2026-34364 AVideo has User Group-Based Category Access Control Bypass via Missing and Broken Group Filtering in categories.json.php — AVideo 5.3 Medium2026-03-27
CVE-2026-4933 Unpublished Node Permissions - Critical - Access bypass - SA-CONTRIB-2026-029 — Unpublished Node Permissions 7.5 -2026-03-26
CVE-2026-3573 AI (Artificial Intelligence) - Moderately critical - Information Disclosure - SA-CONTRIB-2026-028 — AI (Artificial Intelligence) 9.1 -2026-03-26
CVE-2026-3526 File Access Fix (deprecated) - Moderately critical - Access bypass - SA-CONTRIB-2026-021 — File Access Fix (deprecated) 7.5AIHighAI2026-03-26
CVE-2026-3525 File Access Fix (deprecated) - Moderately critical - Access bypass - SA-CONTRIB-2026-020 — File Access Fix (deprecated) 7.5AIHighAI2026-03-26
CVE-2026-33477 FileRise has incorrect authorization in /api/file/snippet.php allows read_own users to read other users’ file content — FileRise 4.3 Medium2026-03-26
CVE-2026-33469 Authenticated Frigate users can read the full unredacted configuration via `/api/config/raw — frigate 6.5 Medium2026-03-26
CVE-2026-33015 EVerest has RemoteStop Bypass via BCB Toggle Session Restart — everest-core 5.2 Medium2026-03-26
CVE-2026-33014 EVerest has Delayed Authorization Response Bypasses Termination After RemoteStop — everest-core 5.2 Medium2026-03-26
CVE-2026-29044 EVerest: Charging Continues When WithdrawAuthorization Is Processed Before TransactionStarted — everest-core 5.0 Medium2026-03-26
CVE-2026-3115 Guest users can view group member IDs without respecting view restrictions — Mattermost 4.3 Medium2026-03-26
CVE-2026-33343 etcd: Nested etcd transactions bypass RBAC authorization checks — etcd--2026-03-26
CVE-2026-4274 Insufficient authorization in shared channel membership sync grants team-level access instead of channel-level access — Mattermost 5.4 Medium2026-03-26
CVE-2026-4263 Incorrect authorization in HiJiffy Chatbot — HiJiffy Chatbot 7.5 -2026-03-26
CVE-2026-4262 Incorrect authorization in HiJiffy Chatbot — HiJiffy Chatbot 7.5 -2026-03-26
CVE-2026-33249 NATS: Message tracing can be redirected to arbitrary subject — nats-server 4.3 Medium2026-03-25
CVE-2026-33217 NATS allows MQTT clients to bypass ACL checks — nats-server 7.1 High2026-03-25
CVE-2026-33722 n8n Has External Secrets Authorization Bypass in Credential Saving — n8n 5.3 -2026-03-25
CVE-2026-33720 n8n Has Authorization Bypass in OAuth Callback via N8N_SKIP_AUTH_ON_OAUTH_CALLBACK — n8n 5.4 -2026-03-25
CVE-2026-2726 Incorrect Authorization in GitLab — GitLab 4.3 Medium2026-03-25

Vulnerabilities classified as CWE-863 (授权机制不正确) represent 1275 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.