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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

6905 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)
Confidentiality Read 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.
Integrity Modify 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 Control Gain Privileges or Assume Identity, Bypass Protection Mechanism
An attacker could gain privileges by modifying or reading critical data directly, or by accessing privileged functionality.
Availability DoS: 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 Design Divide 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 Design Ensure 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 Design Use 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 Design For 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, Installation Use 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 ID Title CVSS Severity Published
CVE-2025-69093 WordPress ShopMagic plugin <= 4.7.2 - Broken Access Control vulnerability — ShopMagic 5.3 Medium 2025-12-30
CVE-2025-69091 WordPress Demo Importer Plus plugin <= 2.0.8 - Broken Access Control vulnerability — Demo Importer Plus 4.3 Medium 2025-12-30
CVE-2025-69028 WordPress weForms plugin <= 1.6.25 - Broken Access Control vulnerability — weForms 5.3 Medium 2025-12-30
CVE-2025-69031 WordPress Arcane theme <= 3.6.6 - Broken Access Control vulnerability — Arcane 5.3 Medium 2025-12-30
CVE-2025-69027 WordPress Product Delivery Date for WooCommerce – Lite plugin <= 3.2.0 - Broken Access Control vulnerability — Product Delivery Date for WooCommerce – Lite 5.3 Medium 2025-12-30
CVE-2025-69024 WordPress BizPrint plugin <= 4.6.7 - Broken Access Control vulnerability — BizPrint 6.5 Medium 2025-12-30
CVE-2025-69023 WordPress Discussion Board plugin <= 2.5.7 - Broken Access Control vulnerability — Discussion Board 4.3 Medium 2025-12-30
CVE-2025-69022 WordPress HR Management Lite plugin <= 3.6 - Broken Access Control vulnerability — HR Management Lite 5.4 Medium 2025-12-30
CVE-2025-69015 WordPress Crowdsignal Forms plugin <= 1.7.2 - Broken Access Control vulnerability — Crowdsignal Forms 3.8 Low 2025-12-30
CVE-2025-69016 WordPress Shortcodes and extra features for Phlox theme plugin <= 2.17.15 - Broken Access Control vulnerability — Shortcodes and extra features for Phlox theme 4.3 Medium 2025-12-30
CVE-2025-69012 WordPress Event Organiser plugin <= 3.12.8 - Broken Access Control vulnerability — Event Organiser 4.3 Medium 2025-12-30
CVE-2025-69010 WordPress Themebeez Toolkit plugin <= 1.3.5 - Broken Access Control vulnerability — Themebeez Toolkit 5.3 Medium 2025-12-30
CVE-2025-69009 WordPress Medicalequipment theme <= 1.0.9 - Broken Access Control vulnerability — Medicalequipment 5.3 Medium 2025-12-30
CVE-2025-69013 WordPress Stratum plugin <= 1.6.1 - Broken Access Control vulnerability — Stratum 4.3 Medium 2025-12-30
CVE-2025-68993 WordPress Share, Print and PDF Products for WooCommerce plugin <= 3.1.2 - Broken Access Control vulnerability — Share, Print and PDF Products for WooCommerce 5.3 Medium 2025-12-30
CVE-2025-68995 WordPress My Sticky Elements plugin <= 2.3.3 - Broken Access Control vulnerability — My Sticky Elements 4.3 Medium 2025-12-30
CVE-2025-68994 WordPress Product Loops for WooCommerce plugin <= 2.1.2 - Broken Access Control vulnerability — Product Loops for WooCommerce 5.3 Medium 2025-12-30
CVE-2025-68981 WordPress HomeFix Elementor Portfolio plugin <= 1.0.1 - Broken Access Control vulnerability — HomeFix Elementor Portfolio 5.3 Medium 2025-12-30
CVE-2025-68982 WordPress DesignThemes LMS Addon plugin <= 2.6 - Broken Access Control vulnerability — DesignThemes LMS Addon 5.3 Medium 2025-12-30
CVE-2025-68980 WordPress WeDesignTech Portfolio plugin <= 1.0.2 - Broken Access Control vulnerability — WeDesignTech Portfolio 5.3 Medium 2025-12-30
CVE-2025-68976 WordPress Eagle Booking plugin <= 1.3.4.3 - Settings Change vulnerability — Eagle Booking 5.4 Medium 2025-12-30
CVE-2025-68036 WordPress CubeWP plugin <= 1.1.27 - Broken Access Control vulnerability — CubeWP 7.5 High 2025-12-29
CVE-2023-41656 WordPress Better Elementor Addons plugin <= 1.3.7 - Broken Access Control vulnerability — Better Elementor Addons 5.4 Medium 2025-12-29
CVE-2025-68498 WordPress JetTabs plugin <= 2.2.12 - Broken Access Control vulnerability — JetTabs 6.5 Medium 2025-12-29
CVE-2025-68503 WordPress JetBlog plugin <= 2.4.7 - Broken Access Control vulnerability — JetBlog 6.5 Medium 2025-12-29
CVE-2025-68861 WordPress Plugin Optimizer plugin <= 1.3.7 - Broken Access Control vulnerability — Plugin Optimizer 7.1 High 2025-12-29
CVE-2025-15068 Account Takeover in Gmission Web FAX — Web Fax 7.7 High 2025-12-29
CVE-2025-36192 Missing Authorization with the DS8900F and DS8A00 Hardware Management Console — DS8A00( R10.1) 6.7 Medium 2025-12-26
CVE-2025-14913 Frontend Post Submission Manager Lite <= 1.2.6 - Incorrect Authorization to Unauthenticated Arbitrary Attachment Deletion — Frontend Post Submission Manager Lite – Frontend Posting WordPress Plugin 5.3 Medium 2025-12-25
CVE-2025-68920 ckermit 安全漏洞 — C-Kermit 8.9 High 2025-12-24

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