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-2022-0984 Moodle 访问控制错误漏洞 — moodle 4.3 -2022-04-29
CVE-2022-23822 Xilinx Zynq-7000 安全漏洞 — Zynq-7000 SoC FSBL 6.8 -2022-04-27
CVE-2022-1466 Red Hat Single Sign-On 安全漏洞 — rhsso 6.5 -2022-04-26
CVE-2020-25167 OSIsoft PI Vision Incorrect Authorization — PI Vision 4.9 Medium2022-04-18
CVE-2022-0920 Salon booking system < 7.6.3 - Customer+ Bookings/Customers Data Disclosure — Salon booking system 7.5 -2022-04-11
CVE-2022-27609 Forcepoint One Endpoint安全漏洞 — One Endpoint 6.0 Medium2022-04-04
CVE-2022-27608 Forcepoint One Endpoint安全漏洞 — One Endpoint 6.0 Medium2022-04-04
CVE-2022-0825 Amelia < 1.0.49 - Customer+ Arbitrary Appointments Status Update — Amelia – Events & Appointments Booking Calendar 5.4 -2022-04-04
CVE-2022-1223 Incorrect Authorization in phpipam/phpipam — phpipam/phpipam 6.5 Medium2022-04-04
CVE-2021-3456 Foreman 安全漏洞 — smart_proxy_salt 7.3 -2022-03-30
CVE-2020-35501 Linux kernel 安全漏洞 — kernel 4.4 -2022-03-30
CVE-2022-0720 Amelia < 1.0.47 - Customer+ Arbitrary Appointments Update and Sensitive Data Disclosure — Amelia – Events & Appointments Booking Calendar 5.4 -2022-03-28
CVE-2021-20290 OpenSC 安全漏洞 — smart_proxy_openscap 7.3 -2022-03-25
CVE-2022-24778 Incorrect Authorization in imgcrypt — imgcrypt 7.5 High2022-03-25
CVE-2022-0981 Quarkus 安全漏洞 — quarkus 8.8 -2022-03-23
CVE-2021-24905 Advanced Contact form 7 DB < 1.8.7 - Subscriber+ Arbitrary File Deletion — Advanced Contact form 7 DB 8.0 -2022-03-21
CVE-2022-24755 Incorrect Authorization in Bareos Director — bareos 8.1 High2022-03-15
CVE-2022-24721 Incorrect Authorization in org.cometd.oort — cometd 8.1 High2022-03-15
CVE-2022-24714 Disclosure of hosts and related data, linked to decommissioned services in Icinga Web 2 — icingaweb2 5.3 Medium2022-03-08
CVE-2021-41241 Advanced permissions is not respected for subfolders in Nextcloud server — security-advisories 4.3 Medium2022-03-08
CVE-2021-24824 Custom Content Shortcode < 4.0.1 - Unauthorised Arbitrary Post Metadata Access — Custom Content Shortcode 4.3 -2022-03-07
CVE-2021-3658 bluez 安全漏洞 — bluez 4.3 -2022-03-02
CVE-2022-0762 Incorrect Authorization in microweber/microweber — microweber/microweber 5.5 Medium2022-02-26
CVE-2022-21706 Multi-use invitations can grant access to other organizations in Zulip — zulip 7.2 High2022-02-25
CVE-2022-21141 Airspan Networks Mimosa Incorrect Authorization — MMP 10.0 Critical2022-02-18
CVE-2020-25722 Samba 权限许可和访问控制问题漏洞 — samba 8.8 -2022-02-18
CVE-2022-0633 UpdraftPlus Free < 1.22.3 & Premium < 2.22.3 - Subscriber+ Backup Download — UpdraftPlus WordPress Backup Plugin (Free) 6.5 -2022-02-17
CVE-2021-3560 polkit 代码问题漏洞 — polkit 7.8 -2022-02-16
CVE-2022-0580 Incorrect Authorization in librenms/librenms — librenms/librenms 7.1 High2022-02-14
CVE-2022-23615 Partial authorization bypass on document save in xwiki-platform — xwiki-platform 5.4 Medium2022-02-09

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