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-30179 MFA Enforcement Bypass in Search APIs — Mattermost 4.3 Medium2025-03-21
CVE-2025-25274 Unauthorized Command Execution in Archived Channels — Mattermost 4.3 Medium2025-03-21
CVE-2025-27933 Unauthorized Private-to-Public Channel Conversion — Mattermost 5.4 Medium2025-03-21
CVE-2025-27715 Auto-Enrollment of Team Admins into Private Channels without explicit consent — Mattermost 3.3 Low2025-03-21
CVE-2024-7039 Improper Privilege Management in open-webui/open-webui — open-webui/open-webui 6.5 -2025-03-20
CVE-2024-9159 Incorrect Authorization in gaizhenbiao/chuanhuchatgpt — gaizhenbiao/chuanhuchatgpt 6.5 -2025-03-20
CVE-2024-9098 Privilege Escalation in lunary-ai/lunary — lunary-ai/lunary 8.1 -2025-03-20
CVE-2024-10109 Incorrect Authorization in mintplex-labs/anything-llm — mintplex-labs/anything-llm 7.6 -2025-03-20
CVE-2024-10275 Improper Role Modification by Admins for Billing Permissions in lunary-ai/lunary — lunary-ai/lunary 8.8 -2025-03-20
CVE-2024-10273 Improper Privilege Management in lunary-ai/lunary — lunary-ai/lunary 6.1 -2025-03-20
CVE-2025-26853 DESCOR INFOCAD 安全漏洞 — Infocad FM 10.0 Critical2025-03-20
CVE-2025-1472 Unauthorized View Access to Site Statistics and Team Statistics — Mattermost 4.3 Medium2025-03-19
CVE-2025-2202 Broken access control vulnerability in the Innovación y Cualificación local administration plugin ajax.php — ajax.php plugin 7.5 -2025-03-17
CVE-2025-2201 Broken access control vulnerability in the Innovación y Cualificación IcProgreso plugin — IcProgreso plugin 6.5 -2025-03-17
CVE-2025-30074 Parallels Desktop 安全漏洞 — Parallels Desktop 7.8 High2025-03-16
CVE-2025-29997 Improper Access Control Vulnerability in CAP back office application — CAP back office application 8.1 -2025-03-13
CVE-2024-7296 Incorrect Authorization in GitLab — GitLab 2.7 Low2025-03-13
CVE-2025-0652 Incorrect Authorization in GitLab — GitLab 4.3 Medium2025-03-13
CVE-2024-55592 Fortinet FortiSIEM 安全漏洞 — FortiSIEM 3.6 Low2025-03-11
CVE-2024-45328 Fortinet FortiSandbox 安全漏洞 — FortiSandbox 7.1 High2025-03-11
CVE-2025-27822 Backdrop CMS 安全漏洞 — Masquerade 7.5 High2025-03-07
CVE-2025-2045 Incorrect Authorization in GitLab — GitLab 4.3 Medium2025-03-06
CVE-2025-1540 Incorrect Authorization in GitLab — GitLab 3.1 Low2025-03-06
CVE-2025-2003 Devolutions Server 安全漏洞 — Server 8.8 -2025-03-05
CVE-2025-0360 AXIS OS 安全漏洞 — AXIS OS 7.8 High2025-03-04
CVE-2025-0359 AXIS OS 安全漏洞 — AXIS OS 8.5 High2025-03-04
CVE-2024-2321 Incorrect Authorization in Multiple WSO2 Products Allows API Access via Refresh Token — WSO2 API Manager 5.6 Medium2025-02-27
CVE-2025-26532 Teachers can evade trusttext config when restoring glossary entries — moodle 3.1 Low2025-02-24
CVE-2025-26531 IDOR in badges allows disabling of arbitrary badges — moodle 3.1 Low2025-02-24
CVE-2025-26526 Feedback response viewing and deletions did not respect Separate Groups mode — moodle 6.5 Medium2025-02-24

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