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-32108 Copyparty ftp/sftp: Sharing a single file did not fully restrict source-folder access — copyparty 7.5AIHighAI2026-03-11
CVE-2026-32101 StudioCMS S3 Storage Manager Authorization Bypass via Missing `await` on Async Auth Check — s3-storage 7.6 High2026-03-11
CVE-2026-31887 Shopware unauthenticated data extraction possible through store-api.order endpoint — core 9.1AICriticalAI2026-03-11
CVE-2026-1471 Caching of authentication context — Enterprise edition 6.5AIMediumAI2026-03-11
CVE-2026-30239 OpenProject has a Permission Check bypass on Budget deletion allows reassignment of WorkPackages into other budgets — openproject 6.5 Medium2026-03-11
CVE-2026-30236 OpenProject users that are not project members can be used to calculate Labor Budget, leaking their global hourly rate — openproject 4.3 Medium2026-03-11
CVE-2026-1524 Auth misconfiguration when multiple providers enabled — Enterprise Edition 7.2AIHighAI2026-03-11
CVE-2025-12555 Incorrect Authorization in GitLab — GitLab 4.3 Medium2026-03-11
CVE-2026-1497 Incorrect privilege assignment in composite databases — Enterprise Edition 9.8AICriticalAI2026-03-11
CVE-2026-31892 WorkflowTemplate Security Bypass via podSpecPatch in Strict/Secure Reference Mode — argo-workflows 8.8 -2026-03-11
CVE-2026-28229 Argo Workflows has unauthorized access to Argo Workflows Template — argo-workflows 9.8 Critical2026-03-11
CVE-2026-32059 OpenClaw 2026.2.22-2 < 2026.2.23 - Allowlist Bypass via sort Long-Option Abbreviation in tools.exec.safeBins — openclaw 8.8 High2026-03-11
CVE-2026-21286 Adobe Commerce | Incorrect Authorization (CWE-863) — Adobe Commerce 5.3 Medium2026-03-11
CVE-2026-21297 Adobe Commerce | Incorrect Authorization (CWE-863) — Adobe Commerce 4.3 Medium2026-03-11
CVE-2026-21359 Adobe Commerce | Incorrect Authorization (CWE-863) — Adobe Commerce 4.7 Medium2026-03-11
CVE-2026-21309 Adobe Commerce | Incorrect Authorization (CWE-863) — Adobe Commerce 7.5 High2026-03-11
CVE-2026-21285 Adobe Commerce | Incorrect Authorization (CWE-863) — Adobe Commerce 4.3 Medium2026-03-11
CVE-2026-21289 Adobe Commerce | Incorrect Authorization (CWE-863) — Adobe Commerce 7.5 High2026-03-11
CVE-2026-21296 Adobe Commerce | Incorrect Authorization (CWE-863) — Adobe Commerce 4.3 Medium2026-03-11
CVE-2026-31838 Istio HTTP debug endpoints on port 15014 to enforce namespace-based authorization, preventing cross-namespace proxy data access. — istio 7.5AIHighAI2026-03-10
CVE-2026-31801 zot create-only policy allows overwrite attempts of existing latest tag (update permission not required) — zot 7.7 High2026-03-10
CVE-2026-30965 Parse Server session token exfiltration via `redirectClassNameForKey` query parameter — parse-server 8.1AIHighAI2026-03-10
CVE-2026-30947 Parse Server ha a bypass of class-level permissions in LiveQuery — parse-server 7.5AIHighAI2026-03-10
CVE-2026-26308 Envoy has an RBAC Header Validation Bypass via Multi-Value Header Concatenation — envoy 7.5 High2026-03-10
CVE-2026-29773 kubewarden-controller cross-namespace data exfiltration via deprecated host callback binding — kubewarden-controller 4.3 Medium2026-03-09
CVE-2026-28513 Pocket ID: OIDC authorization code validation uses AND instead of OR, allowing cross-client token exchange — pocket-id 8.5 High2026-03-09
CVE-2026-30854 Parse Server: GraphQL `__type` introspection bypass via inline fragments when public introspection is disabled — parse-server 5.3 -2026-03-07
CVE-2026-29196 Netmaker: Service User with Network Access Can Access config files with WireGuard Private Keys — netmaker 6.5 -2026-03-07
CVE-2026-29195 Netmaker: Privilege Escalation from Admin to Super-Admin via User Update — netmaker 7.2 -2026-03-07
CVE-2026-29194 Netmaker: Insufficient Authorization in Host Token Verification — netmaker 8.8 -2026-03-07

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