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-66378 Pexip Infinity 安全漏洞 — Infinity 5.9 Medium2025-12-25
CVE-2025-59683 Pexip Infinity 安全漏洞 — Infinity 8.2 High2025-12-25
CVE-2019-25237 V-SOL GPON/EPON OLT Platform 2.03 Privilege Escalation via User Role Parameter — SOL GPON/EPON OLT Platform 9.8 Critical2025-12-24
CVE-2018-25146 Microhard Systems IPn4G 1.1.0 Service Control Denial of Service — Microhard Systems 3G/4G Cellular Ethernet and Serial Gateway Service Control DoS 8.1 High2025-12-24
CVE-2025-2515 Bluechi: privilege escalation in bluechi via unrestricted cross-node systemd dependencies — BlueChi 7.2 High2025-12-24
CVE-2025-64641 Mattermost Jira plugin crafted action leaks Jira issue details — Mattermost 4.1 Medium2025-12-24
CVE-2025-13767 Unauthorized Read Access to Private Channel Posts via Mattermost Jira Plugin — Mattermost 4.3 Medium2025-12-24
CVE-2025-58052 Galette has groups managers access control bypass on Members — galette 6.5AIMediumAI2025-12-19
CVE-2025-53922 Galette has access control bypass — galette 2.7AILowAI2025-12-19
CVE-2025-68422 Kibana Improper Authorization — Kibana 4.3 Medium2025-12-18
CVE-2025-68386 Kibana Improper Authorization — Kibana 4.3 Medium2025-12-18
CVE-2025-14318 Improper access validation in M-Files Server — M-Files Server 6.5AIMediumAI2025-12-18
CVE-2025-47382 Incorrect Authorization in Boot — Snapdragon 7.8 High2025-12-18
CVE-2025-68129 Auth0-PHP SDK has Improper Audience Validation — auth0-PHP 6.8 Medium2025-12-17
CVE-2025-14081 Ultimate Member <= 2.11.0 - Authenticated (Subscriber+) Profile Privacy Setting Bypass — Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin 4.3 Medium2025-12-17
CVE-2025-13324 Lack of Invalidation of Legacy Remote Cluster Invite Tokens After Confirmation — Mattermost 3.7 Low2025-12-17
CVE-2025-14305 Acer|ListCheck.exe - Local Privilege Escalation — ListCheck.exe 7.8 High2025-12-17
CVE-2025-67740 JetBrains TeamCity 安全漏洞 — TeamCity 2.7 Low2025-12-11
CVE-2025-67490 Auth0 Next.js SDK has Improper Request Caching Lookup — nextjs-auth0 5.4 Medium2025-12-10
CVE-2025-9056 Tecno AudioLink 安全漏洞 — com.transsion.audiosmartconnect 7.1AIHighAI2025-12-10
CVE-2025-54838 Fortinet FortiPortal 安全漏洞 — FortiPortal 6.4 Medium2025-12-09
CVE-2025-40819 Siemens SINEMA Remote Connect Server 安全漏洞 — SINEMA Remote Connect Server 4.3 Medium2025-12-09
CVE-2025-66581 Frappe LMS is Missing Server-Side Authorization in Business Logic — lms 8.8 -2025-12-05
CVE-2025-66406 Improper Authorization Check for SSH Certificate Revocation — certificates 5.0 Medium2025-12-03
CVE-2025-20381 SPL commands allowlist controls bypass in Splunk MCP Server app through "run_splunk_query" MCP tool — Splunk MCP Server 5.4 Medium2025-12-03
CVE-2024-32643 Masa CMS vulnerable to authentication bypass with /tag/ — MasaCMS 7.5 High2025-12-03
CVE-2025-12756 Insecure Direct Object Reference in Mattermost Boards Plugin Enables Unauthorised Comment Deletion — Mattermost 4.3 Medium2025-12-01
CVE-2025-13829 Data Illusion Zumbrunn NGSurvey 安全漏洞 — NGSurvey 6.5AIMediumAI2025-12-01
CVE-2025-66423 Tryton trytond 安全漏洞 — trytond 7.1 High2025-11-30
CVE-2025-66433 HTCondor Access Point 安全漏洞 — HTCondor 4.2 Medium2025-11-30

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