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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

5655 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-2025-68009 WordPress Slider Templates plugin <= 1.0.3 - Broken Access Control vulnerability — Slider Templates 6.5 Medium2026-01-22
CVE-2025-68003 WordPress Shown Connector plugin <= 1.2.10 - Settings Change vulnerability — Shown Connector 6.5 Medium2026-01-22
CVE-2025-67967 WordPress Lawyer Directory plugin <= 1.3.3 - Broken Access Control vulnerability — Lawyer Directory 7.6 High2026-01-22
CVE-2025-67958 WordPress TaxCloud for WooCommerce plugin <= 8.3.8 - Broken Access Control vulnerability — TaxCloud for WooCommerce 6.5 Medium2026-01-22
CVE-2025-67956 WordPress User Registration plugin <= 4.4.6 - Broken Access Control vulnerability — User Registration 8.2 High2026-01-22
CVE-2025-67942 WordPress Peach Payments Gateway plugin <= 3.3.6 - Broken Access Control vulnerability — Peach Payments Gateway 6.5 Medium2026-01-22
CVE-2025-67939 WordPress Tickera plugin <= 3.5.6.2 - Broken Access Control vulnerability — Tickera 6.5 Medium2026-01-22
CVE-2025-66141 WordPress Scroller plugin <= 2.0.2 - Broken Access Control vulnerability — Scroller 5.4 Medium2026-01-22
CVE-2025-66142 WordPress Comparimager for Elementor plugin <= 1.0.1 - Broken Access Control vulnerability — Comparimager for Elementor 5.4 Medium2026-01-22
CVE-2025-66143 WordPress Crumber plugin <= 1.0.10 - Broken Access Control vulnerability — Crumber 5.4 Medium2026-01-22
CVE-2025-66137 WordPress Searcher for Elementor plugin <= 1.0.3 - Broken Access Control vulnerability — Searcher for Elementor 5.4 Medium2026-01-22
CVE-2025-66139 WordPress Audier For Elementor plugin <= 1.0.9 - Broken Access Control vulnerability — Audier For Elementor 5.4 Medium2026-01-22
CVE-2025-66136 WordPress Carter for Elementor plugin <= 1.0.2 - Broken Access Control vulnerability — Carter for Elementor 5.4 Medium2026-01-22
CVE-2025-66138 WordPress Motionger for Elementor plugin <= 2.0.4 - Broken Access Control vulnerability — Motionger for Elementor 5.4 Medium2026-01-22
CVE-2025-66140 WordPress Uper for Elementor plugin <= 1.0.5 - Broken Access Control vulnerability — Uper for Elementor 5.4 Medium2026-01-22
CVE-2025-66135 WordPress Imager for Elementor plugin <= 2.0.4 - Broken Access Control vulnerability — Imager for Elementor 5.4 Medium2026-01-22
CVE-2025-62754 WordPress Payment Gateway bKash for WC plugin <= 3.1.0 - Broken Access Control vulnerability — Payment Gateway bKash for WC 5.3 Medium2026-01-22
CVE-2025-63018 WordPress Bard theme <= 2.229 - Broken Access Control vulnerability — Bard 4.3 Medium2026-01-22
CVE-2025-62106 WordPress WP-CRM System plugin <= 3.4.5 - Broken Access Control vulnerability — WP-CRM System 5.4 Medium2026-01-22
CVE-2025-54002 WordPress xSmart theme <= 1.2.9.4 - Broken Access Control vulnerability — xSmart 6.5 Medium2026-01-22
CVE-2025-5805 WordPress Electron theme <= 1.8.2 - Broken Access Control vulnerability — Electron 6.5 Medium2026-01-22
CVE-2025-49375 WordPress HomeLancer theme <= 1.0.1 - Broken Access Control vulnerability — HomeLancer 5.4 Medium2026-01-22
CVE-2026-24042 Appsmith public apps can execute unpublished actions (viewMode confusion) — appsmith 9.4 Critical2026-01-22
CVE-2026-1036 Photo Gallery by 10Web – Mobile-Friendly Image Gallery <= 1.8.36 - Missing Authorization to Unauthenticated Arbitrary Comment Deletion — Photo Gallery by 10Web – Mobile-Friendly Image Gallery 5.3 Medium2026-01-21
CVE-2026-23517 Fleet has an Access Control vulnerability in debug/pprof endpoints — fleet 6.5AIMediumAI2026-01-21
CVE-2026-0554 NotificationX <= 3.1.11 - Missing Authorization to Authenticated (Contributor+) Analytics Reset — NotificationX – FOMO, Live Sales Notification, WooCommerce Sales Popup, GDPR, Social Proof, Announcement Banner & Floating Notification Bar 4.3 Medium2026-01-20
CVE-2025-15347 Creator LMS – The LMS for Creators, Coaches, and Trainers <= 1.1.12 - Missing Authorization to Authenticated (Contributor+) Arbitrary Options Update — Creator LMS – Online Courses and eLearning Plugin 8.8 High2026-01-20
CVE-2025-15043 The Events Calendar <= 6.15.13 - Missing Authorization to Authenticated (Subscriber+) Data Migration Control — The Events Calendar 5.4 Medium2026-01-20
CVE-2026-0548 Tutor LMS – eLearning and online course solution <= 3.9.4 - Missing Authorization to Authenticated (Subscriber+) Limited Attachment Deletion — Tutor LMS – eLearning and online course solution 5.4 Medium2026-01-20
CVE-2025-14798 LearnPress – WordPress LMS Plugin <= 4.3.2.4 - Missing Authorization to Unauthenticated Sensitive User Information Disclosure via REST API — LearnPress – WordPress LMS Plugin for Create and Sell Online Courses 5.3 Medium2026-01-20

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