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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

1278 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-30820 Flowise Authorization Bypass via Spoofed x-request-from Header — Flowise 8.8 -2026-03-07
CVE-2026-30241 Mercurius: queryDepth limit bypassed for WebSocket subscriptions — mercurius 7.5 -2026-03-06
CVE-2026-30229 Parse Server: Endpoint `/loginAs` allows `readOnlyMasterKey` to gain full read and write access as any user — parse-server 9.8 -2026-03-06
CVE-2026-30228 Parse Server: File creation and deletion bypasses `readOnlyMasterKey` write restriction — parse-server 9.1 -2026-03-06
CVE-2026-29182 Parse Server: Cloud Hooks and Cloud Jobs bypass `readOnlyMasterKey` write restriction — parse-server 8.1 -2026-03-06
CVE-2026-29087 @hono/node-server: Authorization bypass for protected static paths via encoded slashes in Serve Static Middleware — node-server 7.5 High2026-03-06
CVE-2026-23925 Unauthorized host creation via configuration.import API by low-privilege user with write permissions — Zabbix 6.5 -2026-03-06
CVE-2026-28726 Acronis Cyber Protect 安全漏洞 — Acronis Cyber Protect 17 7.5 -2026-03-05
CVE-2026-28724 Acronis Cyber Protect 安全漏洞 — Acronis Cyber Protect 17 7.5 -2026-03-05
CVE-2026-28723 Acronis Cyber Protect 安全漏洞 — Acronis Cyber Protect 17 8.2 -2026-03-05
CVE-2026-28720 Acronis Cyber Protect 安全漏洞 — Acronis Cyber Protect 17 5.3 -2026-03-05
CVE-2026-28719 Acronis Cyber Protect 安全漏洞 — Acronis Cyber Protect 17 9.8 -2026-03-05
CVE-2026-28716 Acronis Cyber Protect 安全漏洞 — Acronis Cyber Protect 17 9.8 -2026-03-05
CVE-2026-28715 Acronis Cyber Protect 安全漏洞 — Acronis Cyber Protect 17 6.5 -2026-03-05
CVE-2026-28709 Acronis Cyber Protect 安全漏洞 — Acronis Cyber Protect 17 9.8 -2026-03-05
CVE-2026-28474 OpenClaw Nextcloud Talk < 2026.2.6 - Allowlist Bypass via actor.name Display Name Spoofing — nextcloud-talk 9.8 Critical2026-03-05
CVE-2026-28473 OpenClaw < 2026.2.2 - Authorization Bypass via /approve Chat Command — OpenClaw 8.1 High2026-03-05
CVE-2026-28466 OpenClaw < 2026.2.14 - Remote Code Execution via Node Invoke Approval Bypass — OpenClaw 9.9 Critical2026-03-05
CVE-2026-21621 Improper Scope Enforcement in OAuth client_credentials Flow Allows Read-Only API Key to Escalate to Full Access — hexpm 8.8 -2026-03-05
CVE-2026-3009 Org.keycloak/keycloak-services: improper enforcement of disabled identity provider in identitybrokerservice (authentication bypass) — Red Hat build of Keycloak 26.4 8.1 High2026-03-05
CVE-2026-3236 Octopus Server 安全漏洞 — Octopus Server 7.5 -2026-03-05
CVE-2026-26949 Dell Device Management Agent 安全漏洞 — Device Management Agent (DDMA) 5.5 Medium2026-03-04
CVE-2026-3103 Deletion of passwords via RestApi — Checkmk 7.1AIHighAI2026-03-04
CVE-2026-3136 Google Cloud Build Comment Control Bypass — Cloud Build 9.8AICriticalAI2026-03-03
CVE-2026-2293 NestJS 11.1.13 - Lack of data validation allowing authentication/authorization bypass — nest.js 9.8 -2026-02-27
CVE-2025-9572 Foreman: satellite: graphql api permission bypass leads to information disclosure — Foreman 5.0 Medium2026-02-27
CVE-2026-25741 Zulip Vulnerable to Modification of Payment Method (Stripe Default Card) by Non-Billing Users — zulip 7.1 High2026-02-26
CVE-2026-28227 Discourse Vulnerable to Unauthorized Topic Creation in Staff-Only Categories via Topic Timer publish_to_category — discourse 4.3AIMediumAI2026-02-26
CVE-2026-27153 Discourse doesn't prevent moderators from exporting user Chat DMs — discourse 5.4AIMediumAI2026-02-26
CVE-2026-26973 Discourse doesn't scope reviewable notes to user-visible reviewables — discourse 4.3 Medium2026-02-26

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