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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-862 (授权机制缺失) — Vulnerability Class 5581

5581 vulnerabilities classified as CWE-862 (授权机制缺失). AI Chinese analysis included.

CWE-862 represents a critical access control weakness where software fails to verify an actor’s permissions before granting access to resources or executing actions. Attackers typically exploit this flaw by manipulating requests to access sensitive data or perform privileged operations that should be restricted to authorized users. Without proper checks, malicious actors can bypass authentication mechanisms entirely, leading to unauthorized data exposure, modification, or system compromise. Developers mitigate this risk by implementing robust authorization logic at every entry point, ensuring that identity verification is coupled with strict permission validation. This involves checking user roles and access rights against the requested resource before processing any request. By integrating these checks into the application’s core architecture and utilizing established frameworks, teams can prevent unauthorized access and maintain the integrity of their systems against exploitation.

MITRE CWE Description
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Common Consequences (4)
ConfidentialityRead Application Data, Read Files or Directories
An attacker could read sensitive data, either by reading the data directly from a data store that is not restricted, or by accessing insufficiently-protected, privileged functionality to read the data.
IntegrityModify Application Data, Modify Files or Directories
An attacker could modify sensitive data, either by writing the data directly to a data store that is not restricted, or by accessing insufficiently-protected, privileged functionality to write the data.
Access ControlGain Privileges or Assume Identity, Bypass Protection Mechanism
An attacker could gain privileges by modifying or reading critical data directly, or by accessing privileged functionality.
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 (2)
This function runs an arbitrary SQL query on a given database, returning the result of the query.
function runEmployeeQuery($dbName, $name){ mysql_select_db($dbName,$globalDbHandle) or die("Could not open Database".$dbName); //Use a prepared statement to avoid CWE-89 $preparedStatement = $globalDbHandle->prepare('SELECT * FROM employees WHERE name = :name'); $preparedStatement->execute(array(':name' => $name)); return $preparedStatement->fetchAll(); } /.../ $employeeRecord = runEmployeeQuery('EmployeeDB',$_GET['EmployeeName']);
Bad · PHP
The following program could be part of a bulletin board system that allows users to send private messages to each other. This program intends to authenticate the user before deciding whether a private message should be displayed. Assume that LookupMessageObject() ensures that the $id argument is numeric, constructs a filename based on that id, and reads the message details from that file. Also ass…
sub DisplayPrivateMessage { my($id) = @_; my $Message = LookupMessageObject($id); print "From: " . encodeHTML($Message->{from}) . "<br>\n"; print "Subject: " . encodeHTML($Message->{subject}) . "\n"; print "<hr>\n"; print "Body: " . encodeHTML($Message->{body}) . "\n"; } my $q = new CGI; # For purposes of this example, assume that CWE-309 and # CWE-523 do not apply. if (! AuthenticateUser($q->param('username'), $q->param('password'))) { ExitError("invalid username or password"); } my $id = $q->param('id'); DisplayPrivateMessage($id);
Bad · Perl
CVE IDTitleCVSSSeverityPublished
CVE-2026-23681 Missing Authorization check in a function module in SAP Support Tools Plug-In — SAP Support Tools Plug-In 4.3 Medium2026-02-10
CVE-2026-0509 Missing Authorization check in SAP NetWeaver Application Server ABAP and ABAP Platform — SAP NetWeaver Application Server ABAP and ABAP Platform 9.6 Critical2026-02-10
CVE-2026-0490 Denial of service (DOS) in SAP BusinessObjects BI Platform — SAP BusinessObjects BI Platform 7.5 High2026-02-10
CVE-2026-0488 Code Injection vulnerability in SAP CRM and SAP S/4HANA (Scripting Editor) — SAP CRM and SAP S/4HANA (Scripting Editor) 9.9 Critical2026-02-10
CVE-2026-0486 Missing Authorization Check in ABAP based SAP systems — ABAP based SAP systems 5.0 Medium2026-02-10
CVE-2026-0845 WCFM - WooCommerce Frontend Manager <= 6.7.24 - Authenticated (Shop Manager+) Arbitrary Options Update — WCFM – Frontend Manager for WooCommerce 7.2 High2026-02-09
CVE-2026-25939 FUXA Unauthenticated Remote Arbitrary Scheduler Write — FUXA 9.3AICriticalAI2026-02-09
CVE-2026-25808 Hollo DMs get leaked and can be seen on Webfinger Browser — hollo 7.5 High2026-02-09
CVE-2026-25806 PlaciPy has Missing Authorization Checks on Student Management Endpoints (IDOR) — assessment-placipy 9.1AICriticalAI2026-02-09
CVE-2026-25810 PlaciPy is Missing Object-Level Authorization in student.submission.routes.ts — assessment-placipy 9.1AICriticalAI2026-02-09
CVE-2026-25876 PlaciPy is Missing Authorization on Assessment Results Endpoint — assessment-placipy 7.5AIHighAI2026-02-09
CVE-2026-24777 OpenProject has Improper Access Control on User Management allows user managers to lock admin accounts — openproject 6.7 Medium2026-02-09
CVE-2026-24095 Missing Permission Check on Analyze Configuration Page — Checkmk 4.3AIMediumAI2026-02-09
CVE-2026-2208 WeKan Rules rules.js RulesBleed authorization — WeKan 4.3 Medium2026-02-08
CVE-2025-15476 The Bucketlister <= 0.1.5 - Missing Authorization to Authenticated (Subscriber+) Bucket List Modification — The Bucketlister 4.3 Medium2026-02-07
CVE-2026-25752 FUXA Unauthenticated Remote Arbitrary Device Tag Write — FUXA 7.5AIHighAI2026-02-06
CVE-2026-23632 Gogs user can update repository content with read-only permission — gogs 6.5 Medium2026-02-06
CVE-2026-22592 Gogs is Vulnerable to Denial of Service — gogs 6.5 Medium2026-02-06
CVE-2026-1499 WP Duplicate <= 1.1.8 - Authenticated (Subscriber+) Arbitrary File Upload via 'process_add_site' AJAX Action — WP Duplicate – WordPress Migration Plugin 8.8 High2026-02-06
CVE-2025-10753 OAuth Single Sign On – SSO (OAuth Client) <= 6.26.14 - Missing Authorization — OAuth Single Sign On – SSO (OAuth Client) 5.3 Medium2026-02-06
CVE-2025-15326 Tanium addressed an improper access controls vulnerability in Patch. — Patch 4.3 Medium2026-02-05
CVE-2025-15327 Tanium addressed an improper access controls vulnerability in Deploy. — Deploy 4.3 Medium2026-02-05
CVE-2025-15330 Tanium addressed an improper input validation vulnerability in Deploy. — Deploy 8.8 High2026-02-05
CVE-2025-15289 Tanium addressed an improper access controls vulnerability in Interact. — Interact 3.1 Low2026-02-05
CVE-2026-1927 GreenShift - Animation and Page Builder Blocks <= 12.6 - Missing Authorization to Authenticated (Subscriber+) Information Disclosure of AI API Keys and Stored Cross-Site Scripting via custom_css — Greenshift – animation and page builder blocks 5.4 Medium2026-02-05
CVE-2025-14079 ELEX WordPress HelpDesk & Customer Ticketing System <= 3.3.5 - Missing Authorization to Authenticated (Subscriber+) Settings Update — ELEX WordPress HelpDesk & Customer Ticketing System 5.3 Medium2026-02-05
CVE-2025-13416 ProfileGrid – User Profiles, Groups and Communities <= 5.9.7.2 - Missing Authorization to Authenticated (Subscriber+) Arbitrary User Suspension — ProfileGrid – User Profiles, Groups and Communities 4.3 Medium2026-02-05
CVE-2026-1897 WeKan Position-History Tracking positionHistory.js PositionHistoryBleed authorization — WeKan 4.3 Medium2026-02-05
CVE-2026-25538 Devtron Attributes API Unauthorized Access Leading to API Token Signing Key Leakage — devtron 8.8AIHighAI2026-02-04
CVE-2026-25517 Wagtail has improper permission handling on admin preview endpoints — wagtail 5.3AIMediumAI2026-02-04

Vulnerabilities classified as CWE-862 (授权机制缺失) represent 5581 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.