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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

6902 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-68534 WordPress PDF for WPForms plugin <= 6.3.0 - Broken Access Control vulnerability — PDF for WPForms 6.5 Medium 2026-02-20
CVE-2025-68069 WordPress Directorist plugin <= 8.6.6 - Broken Access Control vulnerability — Directorist 7.1 High 2026-02-20
CVE-2025-68043 WordPress LottieFiles plugin <= 3.0.0 - Broken Access Control vulnerability — LottieFiles 7.3 High 2026-02-20
CVE-2025-68050 WordPress Leadpages plugin <= 1.1.3 - Broken Access Control vulnerability — Leadpages 6.5 Medium 2026-02-20
CVE-2025-68042 WordPress Travelpayouts plugin <= 1.2.2 - Broken Access Control vulnerability — Travelpayouts 6.5 Medium 2026-02-20
CVE-2025-68048 WordPress NextMove Lite plugin <= 2.23.0 - Broken Access Control vulnerability — NextMove Lite 7.5 High 2026-02-20
CVE-2025-68032 WordPress Advanced WC Analytics plugin <= 3.19.0 - Settings Change vulnerability — Advanced WC Analytics 6.5 Medium 2026-02-20
CVE-2025-68026 WordPress LC Wizard plugin <= 2.1.1 - Settings Change vulnerability — LC Wizard 6.5 Medium 2026-02-20
CVE-2025-68024 WordPress Addonify – WooCommerce Wishlist plugin <= 2.0.15 - Settings Change vulnerability — Addonify – WooCommerce Wishlist 6.5 Medium 2026-02-20
CVE-2025-68025 WordPress Addonify Floating Cart For WooCommerce plugin <= 1.2.17 - Broken Access Control vulnerability — Addonify Floating Cart For WooCommerce 6.5 Medium 2026-02-20
CVE-2025-68028 WordPress GA4WP: Google Analytics for WordPress plugin <= 2.10.0 - Broken Access Control vulnerability — GA4WP: Google Analytics for WordPress 6.5 Medium 2026-02-20
CVE-2025-68023 WordPress Addonify – Compare Products For WooCommerce plugin <= 1.1.17 - Settings Change vulnerability — Addonify – Compare Products For WooCommerce 6.5 Medium 2026-02-20
CVE-2025-68022 WordPress Plugin BlueX for WooCommerce plugin <= 3.1.6 - Broken Access Control vulnerability — Plugin BlueX for WooCommerce 7.3 High 2026-02-20
CVE-2025-68005 WordPress Easy Hotel Booking plugin <= 1.9.2 - Broken Access Control vulnerability — Easy Hotel Booking 6.5 Medium 2026-02-20
CVE-2025-68000 WordPress Testimonial Slider plugin <= 2.0.15 - Broken Access Control vulnerability — Testimonial Slider 6.5 Medium 2026-02-20
CVE-2025-68021 WordPress ConveyThis plugin <= 269.9 - Broken Access Control vulnerability — ConveyThis 6.5 Medium 2026-02-20
CVE-2025-67994 WordPress YayCurrency plugin <= 3.3 - Arbitrary Content Deletion vulnerability — YayCurrency 7.5 High 2026-02-20
CVE-2025-67993 WordPress Atarim plugin <= 4.2.1 - Broken Access Control vulnerability — Atarim 6.5 Medium 2026-02-20
CVE-2025-67977 WordPress HAPPY plugin <= 1.0.8 - Broken Access Control vulnerability — HAPPY 8.2 High 2026-02-20
CVE-2025-67974 WordPress WPLegalPages plugin <= 3.5.4 - Broken Access Control vulnerability — WPLegalPages 7.5 High 2026-02-20
CVE-2025-67975 WordPress aDirectory plugin <= 3.0.3 - Broken Access Control vulnerability — aDirectory 6.5 Medium 2026-02-20
CVE-2025-67972 WordPress Zoho ZeptoMail plugin <= 3.2.9 - Broken Access Control vulnerability — Zoho ZeptoMail 4.3 Medium 2026-02-20
CVE-2025-67973 WordPress Sunshine Photo Cart plugin <= 3.5.6.2 - Broken Access Control vulnerability — Sunshine Photo Cart 6.5 Medium 2026-02-20
CVE-2025-67970 WordPress Schedula plugin <= 1.0 - Broken Access Control vulnerability — Schedula 5.9 Medium 2026-02-20
CVE-2025-67969 WordPress UPI QR Code Payment Gateway for WooCommerce plugin <= 1.5.1 - Broken Access Control vulnerability — UPI QR Code Payment Gateway for WooCommerce 6.5 Medium 2026-02-20
CVE-2025-67547 WordPress Konte theme <= 2.4.6 - Broken Access Control vulnerability — Konte 6.5 Medium 2026-02-20
CVE-2025-67624 WordPress Optimize More! – Images plugin <= 1.1.3 - Broken Access Control vulnerability — Optimize More! – Images 6.5 Medium 2026-02-20
CVE-2025-53217 WordPress AIO WP Builder Plugin <= 2.0.2 - Broken Access Control Vulnerability — AIO WP Builder 7.6 High 2026-02-20
CVE-2024-54222 WordPress Seraphinite Accelerator plugin <= 2.22.15 - Authenticated Sensitive Data Exposure vulnerability — Seraphinite Accelerator 4.3 Medium 2026-02-20
CVE-2024-34438 WordPress Shared Files plugin <= 1.7.19 - Broken Access Control vulnerability — Shared Files 5.3 Medium 2026-02-20

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