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-2025-11060 Surrealdb: surrealdb is vulnerable to unauthorized data exposure via live query subscriptions 5.7 Medium2025-09-26
CVE-2025-59824 Omni Wireguard SideroLink potential escape — omni 9.9AICriticalAI2025-09-24
CVE-2025-43806 Liferay Portal和Liferay DXP 安全漏洞 — Portal 6.5AIMediumAI2025-09-22
CVE-2025-59714 Grouper 安全漏洞 — Grouper 6.5 Medium2025-09-19
CVE-2025-10016 Local Privilege Escalation in Sparkle Autoupdate Daemon — Sparkle 7.8AIHighAI2025-09-16
CVE-2025-10015 TCC Bypass via Downloader XPC Service in Sparkle — Sparkle 6.6AIMediumAI2025-09-16
CVE-2025-43789 Liferay Portal和Liferay DXP 安全漏洞 — Portal 9.8 -2025-09-12
CVE-2025-43784 Liferay Portal和Liferay DXP 安全漏洞 — Portal 4.3AIMediumAI2025-09-10
CVE-2025-58134 Zoom Workplace Clients for Windows - Incorrect Authorization — Zoom Workplace Clients for Windows 4.3 Medium2025-09-09
CVE-2025-54246 Adobe Experience Manager | Incorrect Authorization (CWE-863) — Adobe Experience Manager 6.5 Medium2025-09-09
CVE-2025-48042 Before action hooks may execute in certain scenarios despite a request being forbidden — ash 8.8AIHighAI2025-09-07
CVE-2025-23262 NVIDIA ConnectX 安全漏洞 — ConnectX GA 6.3 Medium2025-09-04
CVE-2025-23256 NVIDIA BlueField 安全漏洞 — BlueField GA 8.7 High2025-09-04
CVE-2025-7974 rocket.chat Incorrect Authorization Information Disclosure Vulnerability — rocket.chat 7.5 -2025-09-02
CVE-2025-41031 Multiple vulnerabilities in Deporsite by T-INNOVA — Deporsite 5.3AIMediumAI2025-09-02
CVE-2025-41030 Multiple vulnerabilities in Deporsite by T-INNOVA — Deporsite 5.3AIMediumAI2025-09-02
CVE-2025-3586 Liferay Portal和Liferay DXP 安全漏洞 — Portal 7.2AIHighAI2025-09-01
CVE-2025-54877 Tuleap's special and always there fields permissions are not verified in cross-tracker search — tuleap 5.3 Medium2025-08-29
CVE-2025-25010 Kibana privilege escalation via reporting_user role — Kibana 6.5 Medium2025-08-28
CVE-2025-9376 Block Bad Bots and Stop Bad Bots Crawlers and Spiders and Anti Spam Protection <= 11.58 - Insufficient Authorization to Unauthenticated Blocklist Bypass — Block Bad Bots and Stop Bad Bots Crawlers and Spiders and Anti Spam Protection 6.5 Medium2025-08-28
CVE-2025-5187 Nodes can delete themselves by adding an OwnerReference — Kubernetes 6.7 Medium2025-08-27
CVE-2025-1501 Incorrect authorization for traces request/download in CMC before 25.1.0 — CMC 4.3 Medium2025-08-26
CVE-2025-36157 IBM Engineering Lifecycle Management incorrect authorization — Engineering Lifecycle Management 9.8 Critical2025-08-24
CVE-2025-53971 Channel and Team Membership APIs inadvertently allow loss of Member privileges. — Mattermost 3.8 Low2025-08-21
CVE-2025-49810 Thread summarization allows persistent access to channel — Mattermost 3.5 Low2025-08-21
CVE-2025-57728 JetBrains IntelliJ IDEA 安全漏洞 — IntelliJ IDEA 6.5 Medium2025-08-20
CVE-2025-9228 Insufficient authorization when creating notes — MiR Robots 4.3 Medium2025-08-20
CVE-2025-55213 OpenFGA Authorization Bypass (Check) — openfga 9.8 -2025-08-18
CVE-2025-55205 Capsule tenant owners with "patch namespace" permission can hijack system namespaces label — capsule 9.1 Critical2025-08-18
CVE-2025-36120 IBM Storage Virtualize privilege escalation — Storage Virtualize 8.8 High2025-08-18

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