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-41423 Unauthorized Playbooks Post Deletion in Mattermost Playbooks Plugin — Mattermost 3.1 Low2025-04-24
CVE-2024-10306 Mod_proxy_cluster: mod_proxy_cluster unauthorized mcmp requests 5.4 Medium2025-04-23
CVE-2024-12862 REST API allows users without permissions to remove external collaborators — Content Server 4.3 -2025-04-21
CVE-2025-3838 Improper Authorization in the installer for the EOL OVA based connect component — OVA based Connect 8.8 -2025-04-21
CVE-2025-43922 FileWave Windows client 安全漏洞 — FileWave 8.1 High2025-04-21
CVE-2025-32408 Soffid Console 安全漏洞 — IAM 2.5 Low2025-04-21
CVE-2025-43921 GNU Mailman 安全漏洞 — Mailman 5.3 Medium2025-04-20
CVE-2025-43917 Pritunl Client 安全漏洞 — Pritunl-Client 8.2 High2025-04-19
CVE-2024-49808 IBM Sterling Connect:Direct Web Services improper authorization — Sterling Connect:Direct Web Services 6.3 Medium2025-04-18
CVE-2025-3453 Password Protected – Password Protect your WordPress Site, Pages, & WooCommerce Products <= 2.7.7 - Unauthenticated Sensitive Information Exposure — Password Protected — Lock Entire Site, Pages, Posts, Categories, and Partial Content 5.3 Medium2025-04-17
CVE-2025-2564 Unauthorized View Access to Archived Channel Member Info — Mattermost 4.3 Medium2025-04-16
CVE-2025-27571 Channel metadata visible in archived channels despite configuration setting — Mattermost 4.3 Medium2025-04-16
CVE-2025-24839 Unauthorized AI bot activation via Wrangler plugin — Mattermost 3.1 Low2025-04-16
CVE-2025-2424 Leaked Metadata of Deleted Files via Bookmark Creation — Mattermost 3.1 Low2025-04-14
CVE-2025-32093 Syatem admin profile modification by delegated granular administration role — Mattermost 4.7 Medium2025-04-14
CVE-2025-32068 Revoking authorization of OAuth2 consumer does not invalidate refresh tokens — Mediawiki - OAuth Extension 9.8AICriticalAI2025-04-11
CVE-2025-24866 Unauthorized Access to User Activity Logs API by delegated granular administration roles — Mattermost 2.7 Low2025-04-10
CVE-2025-26330 Dell PowerScale OneFS 安全漏洞 — PowerScale OneFS 7.0 High2025-04-10
CVE-2025-27188 Adobe Commerce | Incorrect Authorization (CWE-863) — Adobe Commerce 4.3 Medium2025-04-08
CVE-2025-31331 Authorization Bypass vulnerability in SAP NetWeaver — SAP NetWeaver 4.3 Medium2025-04-08
CVE-2025-31481 GraphQL query operations security can be bypassed — core 7.5 High2025-04-03
CVE-2025-27427 Apache ActiveMQ Artemis: Address routing-type can be updated by user without the createAddress permission — Apache ActiveMQ Artemis 6.5 -2025-04-01
CVE-2025-31673 Drupal core - Moderately critical - Access bypass - SA-CORE-2025-002 — Drupal core 6.5 -2025-03-31
CVE-2025-30155 Tuleap does not enforce read permissions on parent trackers in the REST API — tuleap 4.3 Medium2025-03-31
CVE-2025-30209 Tuleap has improper permission handling in the REST endpoints and release notes display of the FRS plugin — tuleap 5.3 Medium2025-03-31
CVE-2025-2242 Incorrect Authorization in GitLab — GitLab 7.5 High2025-03-27
CVE-2025-30741 Pixelfed 安全漏洞 — Pixelfed 4.3 Medium2025-03-25
CVE-2025-30163 Node based network policies may incorrectly allow workload traffic — cilium 3.4 Low2025-03-24
CVE-2025-30162 East-west traffic not subject to egress policy enforcement for requests via Gateway API load balancers — cilium 3.2 Low2025-03-24
CVE-2025-24920 Unauthorized Bookmark Creation and Modification in Archived Channels — Mattermost 4.3 Medium2025-03-21

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