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-68603 WordPress Editorial Calendar plugin <= 3.8.8 - Broken Access Control vulnerability — Editorial Calendar 5.4 Medium 2025-12-24
CVE-2025-68594 WordPress Poll, Survey & Quiz Maker Plugin by Opinion Stage plugin <= 19.12.0 - Broken Access Control vulnerability — Poll, Survey & Quiz Maker Plugin by Opinion Stage 5.3 Medium 2025-12-24
CVE-2025-68596 WordPress Bit Assist plugin <= 1.5.11 - Broken Access Control vulnerability — Bit Assist 5.3 Medium 2025-12-24
CVE-2025-68595 WordPress Widgets for Social Photo Feed plugin <= 1.8 - Broken Access Control vulnerability — Widgets for Social Photo Feed 5.3 Medium 2025-12-24
CVE-2025-68591 WordPress Simple File List plugin <= 6.1.18 - Broken Access Control vulnerability — Simple File List 5.4 Medium 2025-12-24
CVE-2025-68592 WordPress WP Adminify plugin <= 4.0.6.1 - Broken Access Control vulnerability — WP Adminify 4.3 Medium 2025-12-24
CVE-2025-68593 WordPress WP Adminify plugin <= 4.0.6.1 - Broken Access Control vulnerability — WP Adminify 5.4 Medium 2025-12-24
CVE-2025-68588 WordPress TS Poll plugin <= 2.5.5 - Broken Access Control vulnerability — TS Poll 4.3 Medium 2025-12-24
CVE-2025-68589 WordPress WP Telegram Widget and Join Link plugin <= 2.2.12 - Broken Access Control vulnerability — WP Telegram Widget and Join Link 5.3 Medium 2025-12-24
CVE-2025-68587 WordPress Watu Quiz plugin <= 3.4.5 - Broken Access Control vulnerability — Watu Quiz 4.3 Medium 2025-12-24
CVE-2025-68586 WordPress Cooked plugin <= 1.11.3 - Broken Access Control vulnerability — Cooked 5.3 Medium 2025-12-24
CVE-2025-68585 WordPress WP Document Revisions plugin <= 3.7.2 - Broken Access Control vulnerability — WP Document Revisions 2.7 Low 2025-12-24
CVE-2025-68581 WordPress YITH Slider for page builders plugin <= 1.0.11 - Broken Access Control vulnerability — YITH Slider for page builders 5.4 Medium 2025-12-24
CVE-2025-68582 WordPress Funnelforms Free plugin <= 3.8 - Broken Access Control vulnerability — Funnelforms Free 5.3 Medium 2025-12-24
CVE-2025-68579 WordPress FV Simpler SEO plugin <= 1.9.6 - Broken Access Control vulnerability — FV Simpler SEO 5.3 Medium 2025-12-24
CVE-2025-68578 WordPress Addonify plugin <= 2.0.4 - Broken Access Control vulnerability — Addonify 5.3 Medium 2025-12-24
CVE-2025-68577 WordPress Virusdie plugin <= 1.1.6 - Broken Access Control vulnerability — Virusdie 4.3 Medium 2025-12-24
CVE-2025-68575 WordPress Wappointment plugin <= 2.7.6 - Broken Access Control vulnerability — Wappointment 5.3 Medium 2025-12-24
CVE-2025-68572 WordPress BBP Core plugin <= 1.4.1 - Broken Access Control vulnerability — BBP Core 5.3 Medium 2025-12-24
CVE-2025-68571 WordPress SALESmanago plugin <= 3.9.0 - Broken Access Control vulnerability — SALESmanago & Leadoo 5.3 Medium 2025-12-24
CVE-2025-68569 WordPress WP Time Slots Booking Form plugin <= 1.2.39 - Broken Access Control vulnerability — WP Time Slots Booking Form 6.5 Medium 2025-12-24
CVE-2025-68568 WordPress Claspo – Popups, Spin the Wheel & Email Capture plugin <= 1.0.7 - Broken Access Control vulnerability — Claspo – Popups, Spin the Wheel & Email Capture 5.3 Medium 2025-12-24
CVE-2025-68565 WordPress Twitch Player plugin <= 2.1.3 - Broken Access Control vulnerability — Twitch Player 5.3 Medium 2025-12-24
CVE-2023-40679 WordPress Master Elementor Addons plugin <= 2.0.5.3 - Broken Access Control vulnerability — Master Addons for Elementor 6.5 Medium 2025-12-24
CVE-2023-28619 WordPress Resoto theme <= 1.0.8 - Broken Access Control to Arbitrary Plugin Activation — Resoto 4.3 Medium 2025-12-24
CVE-2025-68608 WordPress Userpro plugin <= 5.1.9 - Broken Access Control vulnerability — Userpro 7.5 High 2025-12-24
CVE-2025-68535 WordPress Sunshine Photo Cart plugin <= 3.5.7.1 - Broken Access Control vulnerability — Sunshine Photo Cart 4.3 Medium 2025-12-24
CVE-2025-68522 WordPress WpStream plugin <= 4.9.5 - Broken Access Control vulnerability — WpStream 4.3 Medium 2025-12-24
CVE-2025-68523 WordPress Spiffy Calendar plugin <= 5.0.7 - Broken Access Control vulnerability — Spiffy Calendar 4.3 Medium 2025-12-24
CVE-2025-68521 WordPress WpStream plugin <= 4.9.5 - Broken Access Control vulnerability — WpStream 5.3 Medium 2025-12-24

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