Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-863 (授权机制不正确) — Vulnerability Class 1275

1275 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-2026-35491 Pi-hole FTL: CLI API sessions can import Teleporter archives and modify configuration — FTL 6.1 Medium2026-04-07
CVE-2026-35490 changedetection.io has an Authentication Bypass via Decorator Ordering — changedetection.io 9.8 Critical2026-04-07
CVE-2026-5384 runZero Platform incorrect credential scope — Platform 5.8 Medium2026-04-07
CVE-2026-5383 runZero Explorer missing authorization check — Explorer 4.4 Medium2026-04-07
CVE-2026-5382 runZero Platform MCP endpoint information leak — Platform 3.0 Low2026-04-07
CVE-2026-5381 runZero Platform task information leak — Platform 2.2 Low2026-04-07
CVE-2026-5380 runZero Platform cleartext secret exposure — Platform 5.3 Medium2026-04-07
CVE-2026-5379 runZero Platform MCP certification information leak — Platform 3.0 Low2026-04-07
CVE-2026-5378 runZero Platform user creation leak — Platform 5.8 Medium2026-04-07
CVE-2026-5374 runZero Platform MCP information leak — Platform 5.8 Medium2026-04-07
CVE-2026-28808 ScriptAlias CGI targets bypass directory auth in inets httpd (mod_auth vs mod_cgi path mismatch) — OTP 9.8AICriticalAI2026-04-07
CVE-2026-35412 Directus has a TUS Upload Authorization Bypass Allows Arbitrary File Overwrite — directus 7.1 High2026-04-06
CVE-2026-34972 OpenFGA's BatchCheck within-request deduplication produces incorrect authorization decisions via list-value cache-key collision — openfga 5.0 Medium2026-04-06
CVE-2026-35029 LiteLLM affected by privilege escalation via unrestricted proxy configuration endpoint — litellm 8.8AIHighAI2026-04-06
CVE-2026-34953 PraisonAI: Authentication Bypass in OAuthManager.validate_token() — PraisonAI 9.1 Critical2026-04-03
CVE-2026-27447 OpenPrinting CUPS: Authorization bypass via case-insensitive group-member lookup — cups 4.8 Medium2026-04-03
CVE-2025-68153 Juju: Resource poisoning — juju 6.5AIMediumAI2026-04-03
CVE-2025-68152 Juju: Read All Controller Logs From Compromised Workload — juju 6.5AIMediumAI2026-04-03
CVE-2026-34376 PdfDing: Password-protected share bypass via direct serve endpoint — PdfDing 7.5 High2026-04-01
CVE-2025-71278 XenForo OAuth2 Unauthorized Scope Request — XenForo 8.8 High2026-04-01
CVE-2026-34453 SiYuan: Broken access control in /api/bookmark/getBookmark allows unauthenticated publish visitors to read password-protected bookmarked content — siyuan 7.5 High2026-03-31
CVE-2026-34586 PdfDing: Shared PDF Expiration, Max Views, and Deletion Bypass via Serve/Download Endpoints — PdfDing 6.5 Medium2026-03-31
CVE-2026-32726 SciTokens C++: Sibling-Path Authorization Bypass — scitokens-cpp 8.1 High2026-03-31
CVE-2026-34532 Parse Server: Cloud function validator bypass via prototype chain traversal — parse-server 9.1AICriticalAI2026-03-31
CVE-2026-33579 OpenClaw < 2026.3.28 - Privilege Escalation via Missing Caller Scope Validation in Device Pair Approval — OpenClaw 9.9 Critical2026-03-31
CVE-2026-33578 OpenClaw < 2026.3.28 - Sender Policy Allowlist Bypass via Policy Downgrade in Google Chat and Zalouser Extensions — OpenClaw 4.3 Medium2026-03-31
CVE-2026-33576 OpenClaw < 2026.3.28 - Unauthorized Media Download via Zalo Channel — OpenClaw 6.5 Medium2026-03-31
CVE-2026-33577 OpenClaw < 2026.3.28 - Insufficient Scope Validation in node.pair.approve — OpenClaw 8.1 High2026-03-31
CVE-2026-34506 OpenClaw < 2026.3.8 - Sender Allowlist Bypass in Microsoft Teams Plugin via Route Allowlist Configuration — OpenClaw 4.3 Medium2026-03-31
CVE-2026-0562 Insecure Direct Object Reference (IDOR) in parisneo/lollms — parisneo/lollms 6.5 -2026-03-29

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