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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

6908 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-67582 WordPress Wbcom Designs plugin <= 2.1.1 - Broken Access Control vulnerability — Wbcom Designs 5.3 Medium 2025-12-09
CVE-2025-67586 WordPress Highlight and Share plugin <= 5.2.0 - Broken Access Control vulnerability — Highlight and Share 4.7 Medium 2025-12-09
CVE-2025-67584 WordPress GoDAM plugin <= 1.4.6 - Broken Access Control vulnerability — GoDAM 5.3 Medium 2025-12-09
CVE-2025-67583 WordPress IDonate plugin <= 2.1.15 - Broken Access Control vulnerability — IDonate 5.3 Medium 2025-12-09
CVE-2025-67580 WordPress Constant Contact + WooCommerce plugin <= 2.4.1 - Broken Access Control vulnerability — Constant Contact + WooCommerce 5.3 Medium 2025-12-09
CVE-2025-67581 WordPress TrueBooker plugin <= 1.1.0 - Broken Access Control vulnerability — TrueBooker 5.3 Medium 2025-12-09
CVE-2025-67578 WordPress WP Email Capture plugin <= 3.12.4 - Broken Access Control vulnerability — WP Email Capture 5.3 Medium 2025-12-09
CVE-2025-67579 WordPress User Extra Fields plugin <= 16.8 - Broken Access Control vulnerability — User Extra Fields 5.3 Medium 2025-12-09
CVE-2025-67575 WordPress Sitewide Notice WP plugin <= 2.4.1 - Broken Access Control vulnerability — Sitewide Notice WP 5.3 Medium 2025-12-09
CVE-2025-67577 WordPress Easy Form Builder plugin <= 3.8.20 - Broken Access Control vulnerability — Easy Form Builder 5.3 Medium 2025-12-09
CVE-2025-67576 WordPress Simple Link Directory plugin <= 8.8.3 - Broken Access Control vulnerability — Simple Link Directory 5.3 Medium 2025-12-09
CVE-2025-67574 WordPress Booking calendar, Appointment Booking System plugin <= 3.2.30 - Broken Access Control vulnerability — Booking calendar, Appointment Booking System 5.3 Medium 2025-12-09
CVE-2025-67570 WordPress WPForms Google Sheet Connector plugin <= 4.0.0 - Broken Access Control vulnerability — WPForms Google Sheet Connector 5.3 Medium 2025-12-09
CVE-2025-67572 WordPress PenNews theme < 6.7.4 - Broken Access Control vulnerability — PenNews 5.3 Medium 2025-12-09
CVE-2025-67569 WordPress AdForest theme <= 6.0.11 - Broken Access Control vulnerability — AdForest 5.3 Medium 2025-12-09
CVE-2025-67573 WordPress Sailing theme < 4.4.6 - Broken Access Control vulnerability — Sailing 5.3 Medium 2025-12-09
CVE-2025-67571 WordPress WPFunnels plugin <= 3.6.2 - Broken Access Control vulnerability — WPFunnels 5.3 Medium 2025-12-09
CVE-2025-67566 WordPress Woffice Core plugin <= 5.4.30 - Broken Access Control vulnerability — Woffice Core 5.3 Medium 2025-12-09
CVE-2025-67568 WordPress Basel theme <= 5.9.1 - Broken Access Control vulnerability — Basel 5.3 Medium 2025-12-09
CVE-2025-67563 WordPress Post SMTP plugin <= 3.6.1 - Broken Access Control vulnerability — Post SMTP 5.3 Medium 2025-12-09
CVE-2025-67562 WordPress Image Caption Hover Pro plugin < 20.0 - Broken Access Control vulnerability — Image Caption Hover Pro 5.4 Medium 2025-12-09
CVE-2025-67561 WordPress Debug Log Viewer plugin <= 2.0.3 - Broken Access Control vulnerability — Debug Log Viewer 5.4 Medium 2025-12-09
CVE-2025-67560 WordPress Listdom plugin <= 5.0.1 - Broken Access Control vulnerability — Listdom 5.4 Medium 2025-12-09
CVE-2025-67559 WordPress Online Booking & Scheduling Calendar for WordPress by vcita plugin <= 4.5.5 - Broken Access Control vulnerability — Online Booking & Scheduling Calendar for WordPress by vcita 5.4 Medium 2025-12-09
CVE-2025-67548 WordPress WP Delicious plugin <= 1.9.1 - Broken Access Control vulnerability — WP Delicious 6.5 Medium 2025-12-09
CVE-2025-67540 WordPress Animation Addons for Elementor plugin <= 2.4.5 - Arbitrary Content Deletion vulnerability — Animation Addons for Elementor 6.5 Medium 2025-12-09
CVE-2025-67474 WordPress ForumWP plugin <= 2.1.4 - Broken Access Control vulnerability — ForumWP 4.3 Medium 2025-12-09
CVE-2025-67468 WordPress Integration for Salesforce and Contact Form 7, WPForms, Elementor, Formidable, Ninja Forms plugin <= 1.4.6 - Broken Access Control vulnerability — Integration for Salesforce and Contact Form 7, WPForms, Elementor, Formidable, Ninja Forms 4.3 Medium 2025-12-09
CVE-2025-66534 WordPress The Aisle theme <= 2.9 - Broken Access Control vulnerability — The Aisle 4.3 Medium 2025-12-09
CVE-2025-66532 WordPress Powerlift theme < 3.2.1 - Broken Access Control vulnerability — Powerlift 4.3 Medium 2025-12-09

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