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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

1971 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)
Confidentiality Read 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.
Integrity Modify 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 Control Gain 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, Availability Execute Unauthorized Code or Commands
An attacker could use elevated privileges to execute unauthorized commands or code.
Availability DoS: 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 Design Divide 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 Design Ensure 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 Design Use 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 Design For 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, Installation Use 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 ID Title CVSS Severity Published
CVE-2026-16941 IBM i is Affected By An Incorrect Authorization Vulnerability [] — i 4.3 Medium 2026-09-04
CVE-2026-19283 IBM Instana Observability is affected by multiple vulnerabilities within Instana Agent container image — Observability with Instana (Agent) 7.7 High 2026-09-04
CVE-2026-85697 Documenso 2.17.0 PDF Route Ignores Document Visibility — documenso 6.5 Medium 2026-09-04
CVE-2026-85622 AppFlowy-Cloud through 0.9.64 Cross-Workspace Collab Read via WebSocket — AppFlowy-Cloud 5.3 Medium 2026-09-04
CVE-2026-85620 Postgres MCP Pro 0.3.0 Restricted-Mode Bypass via FROM-Clause Function — postgres-mcp 8.6 High 2026-09-04
CVE-2026-85619 AppFlowy-Cloud 0.9.64 Cross-Workspace Collab Access via HTTP API — AppFlowy-Cloud 7.5 High 2026-09-04
CVE-2026-85597 Traefik before v2.11.55 mTLS Bypass via TLS Option Conflict — traefik 8.2 High 2026-09-04
CVE-2026-85592 phpMyFAQ before 4.1.8 Authorization Bypass via question/create — phpMyFAQ 3.7 Low 2026-09-04
CVE-2026-85587 phpMyFAQ before 4.1.8 Incorrect Authorization via Admin Pages — phpMyFAQ 5.3 Medium 2026-09-04
CVE-2026-4644 Improper Authorization in Google Cloud Integration Connectors Leads to Project Takeover — Integration Connectors 8.5 High 2026-09-04
CVE-2026-85538 MISP Attribute Deletion Authorization Bypass Allows Users Without Modify Permissions to Delete Attributes — misp 8.3 High 2026-09-04
CVE-2026-82302 Incorrect Authorization in Kibana Leading to Unauthorized Configuration Modification — Kibana 8.1 High 2026-09-03
CVE-2026-82299 Incorrect Authorization in Kibana Leading to Information Disclosure — Kibana 6.5 Medium 2026-09-03
CVE-2026-82298 Incorrect Authorization in Kibana Leading to Denial of Service — Kibana 4.3 Medium 2026-09-03
CVE-2026-78583 Incorrect Authorization in Kibana Leading to Privilege Escalation — Kibana 8.1 High 2026-09-03
CVE-2026-82023 LearnPress WordPress Plugin < 4.4.6 Broken Object-Level Authorization via Quiz Answer Insert — LearnPress 4.3 Medium 2026-09-03
CVE-2026-85166 n8n before 2.36.2 Credential Exfiltration via Workflow Tool Node — n8n 7.2 High 2026-09-03
CVE-2026-74769 Dell PowerProtect Data Manager 授权问题漏洞 — PowerProtect Data Manager 6.5 Medium 2026-09-03
CVE-2026-85093 Cheshire Cat AI Memory Collection Endpoint Information Disclosure — core 6.5 Medium 2026-09-03
CVE-2026-77122 Nexus Repository 3 - Incorrect Authorization Allows Disclosure of Member Repository Metadata via Group Repository Permissions — Nexus Repository 3 5.3 Medium 2026-09-02
CVE-2026-77125 Nexus Repository 3 - Incorrect Authorization on Blobstore Group Endpoints — Nexus Repository 3 7.1 High 2026-09-02
CVE-2026-82293 Incorrect Authorization in Kibana Leading to Unauthorized Resource Consumption — Kibana 4.3 Medium 2026-09-02
CVE-2026-78587 Incorrect Authorization in Fleet Server Leading to Denial of Service of Agent Upload Operations — Fleet Server 3.1 Low 2026-09-02
CVE-2026-78598 Incorrect Authorization in Kibana Leading to Unauthorized Cross-Space Exposure of Machine Learning Job Data — Kibana 5.4 Medium 2026-09-02
CVE-2026-78609 Incorrect Authorization in Elastic Cloud on Kubernetes Leading to Unauthorized Modification of Data — Eck Operator 5.4 Medium 2026-09-02
CVE-2026-73475 Commerce PayPal - Moderately critical - Access bypass - SA-CONTRIB-2026-095 — Commerce PayPal - - 2026-09-02
CVE-2026-73478 Diff - Moderately critical - Access bypass - SA-CONTRIB-2026-096 — Diff - - 2026-09-02
CVE-2026-73477 Quick Tabs - Moderately critical - Access bypass - SA-CONTRIB-2026-099 — Quick Tabs - - 2026-09-02
CVE-2026-81165 Blazy - Less critical - Access bypass - SA-CONTRIB-2026-104 — Blazy - - 2026-09-02
CVE-2026-81158 Entity API - Moderately critical - Information disclosure - SA-CONTRIB-2026-113 — Entity API - - 2026-09-02

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