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-2021-29943 Apache Solr Unprivileged users may be able to perform unauthorized read/write to collections — Apache Solr 9.1 -2021-04-13
CVE-2020-36287 Atlassian JIRA Server和Atlassian JIRA Data Center 安全漏洞 — Jira Server 5.3 -2021-04-09
CVE-2021-24207 WP Page Builder < 1.2.4 - Insecure default configuration Allows Subscribers Editing Access to Posts — WP Page Builder 4.3 -2021-04-05
CVE-2020-36238 Atlassian Jira Server and Data Center 安全漏洞 — Jira Server 5.3 -2021-04-01
CVE-2021-21411 Incorrect authorization in OAuth2-Proxy — oauth2-proxy 5.5 Medium2021-03-26
CVE-2021-21389 BuddyPress privilege escalation via REST API — BuddyPress 8.1 High2021-03-26
CVE-2021-20283 Moodle 安全漏洞 — moodle 4.3 -2021-03-15
CVE-2021-20282 Moodle 安全漏洞 — moodle 7.5 -2021-03-15
CVE-2020-25239 Siemens SINEMA Remote Connect Server 安全漏洞 — SINEMA Remote Connect Server 8.8 -2021-03-15
CVE-2020-25240 Siemens SINEMA Remote Connect Server 安全漏洞 — SINEMA Remote Connect Server 8.3 -2021-03-15
CVE-2021-20179 pki-core 安全漏洞 — pki-core 7.4 -2021-03-15
CVE-2021-21367 Incorrect Authorization in switchboard-plug-bluetooth — switchboard-plug-bluetooth 6.1 Medium2021-03-12
CVE-2021-26563 Synology DiskStation Manager 访问控制错误漏洞 — DiskStation Manager (DSM) 8.2 High2021-02-26
CVE-2021-20229 PostgreSQL 安全漏洞 — PostgreSQL 4.3 -2021-02-23
CVE-2021-21318 Removing access may not effect published series — opencast 5.4 Medium2021-02-18
CVE-2021-20188 Podman 访问控制错误漏洞 — podman 7.0 -2021-02-11
CVE-2021-21286 Authorization Bypass in AVideo Platform — AVideo 7.7 High2021-02-01
CVE-2021-21276 Privilege escalation in Polr — polr 9.3 Critical2021-02-01
CVE-2020-1725 Red Hat Keycloak 访问控制错误漏洞 — keycloak 5.4 -2021-01-28
CVE-2021-21013 Magento Commerce Insecure Direct Object Reference Could Lead To Information Disclosure — Magento Commerce 8.1 High2021-01-13
CVE-2021-1144 Cisco Connected Mobile Experiences Privilege Escalation Vulnerability — Cisco Connected Mobile Experiences 8.8 High2021-01-13
CVE-2021-1143 Cisco Connected Mobile Experiences User Enumeration Vulnerability — Cisco Connected Mobile Experiences 4.3 Medium2021-01-13
CVE-2020-26250 Base class whitelist configuration ignored in OAuthenticator — oauthenticator 6.3 Medium2020-12-01
CVE-2020-15248 Privilege escalation by backend users assigned to the default "Publisher" system role — october 4.0 Medium2020-11-23
CVE-2020-15246 Local File Inclusion by unauthenticated users — october 7.5 High2020-11-23
CVE-2020-28211 Schneider Electric EcoStruxure Control Expert 权限许可和访问控制问题漏洞 — PLC Simulator on EcoStruxureª Control Expert (now Unity Pro) (all versions) 7.8 -2020-11-19
CVE-2020-25699 Moodle 访问控制错误漏洞 — moodle 7.5 -2020-11-19
CVE-2020-26223 Authorization bypass in Spree — spree 7.7 High2020-11-13
CVE-2020-25655 Red Hat Advanced Cluster Management 安全漏洞 — open-cluster-management 5.7 Medium2020-11-09
CVE-2020-24401 Incorrect permissions following the deletion of a user role or deactivation of a user — Magento Commerce 6.5 Medium2020-11-09

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