目标达成 感谢每一位支持者 — 我们达成了 100% 目标!

目标: 1000 元 · 已筹: 1325

100%

CWE-862 授权机制缺失 类漏洞列表 5967

CWE-862 授权机制缺失 类弱点 5967 条 CVE 漏洞汇总,含 AI 中文分析。

CWE-862 属于缺失授权漏洞,指产品在用户访问资源或执行操作时未进行权限校验。攻击者通常通过直接修改请求参数或构造恶意 URL,绕过前端限制以访问未授权数据或执行敏感操作。开发者应避免仅依赖前端验证,需在服务端对每个请求实施严格的身份认证与权限检查,确保用户仅能访问其被授权的资源,从而从根本上消除越权风险。

MITRE CWE 官方描述
CWE:CWE-862 Missing Authorization(缺失授权) 英文:当主体尝试访问资源或执行操作时,产品未执行授权检查。
常见影响 (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.
缓解措施 (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.
代码示例 (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标题CVSS风险等级Published
CVE-2025-32201 WordPress plugin Xpro Theme Builder 安全漏洞 — Xpro Theme Builder 4.3 Medium2025-04-04
CVE-2025-32147 WordPress plugin Easy WP Optimizer 安全漏洞 — Easy WP Optimizer 8.8 High2025-04-04
CVE-2025-22285 WordPress plugin Pallet Packaging for WooCommerce 安全漏洞 — Pallet Packaging for WooCommerce 8.2 -2025-04-04
CVE-2025-31381 WordPress plugin Booking Calendar and Notification 安全漏洞 — Booking Calendar and Notification 6.5 Medium2025-04-04
CVE-2025-2075 WordPress plugin Uncanny Automator 安全漏洞 — Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin 8.8 High2025-04-04
CVE-2025-31909 WordPress plugin Apptivo Business Site CRM 安全漏洞 — Apptivo Business Site CRM 7.5 High2025-04-03
CVE-2025-31896 WordPress plugin GetBookingsWP 安全漏洞 — GetBookingsWP 6.5 Medium2025-04-03
CVE-2025-31841 WordPress plugin FPW Category Thumbnails 安全漏洞 — FPW Category Thumbnails 6.3 Medium2025-04-03
CVE-2025-31876 WordPress plugin Payday 安全漏洞 — Payday 5.8 Medium2025-04-03
CVE-2025-31858 WordPress plugin Local Magic 安全漏洞 — Local Magic 6.5 Medium2025-04-03
CVE-2025-31794 WordPress plugin WR Price List Manager For Woocommerce 安全漏洞 — WR Price List Manager For Woocommerce 5.4 Medium2025-04-03
CVE-2025-31768 WordPress plugin OTWthemes Widget Manager Light 安全漏洞 — Widget Manager Light 6.5 Medium2025-04-03
CVE-2025-31789 WordPress plugin Matat Technologies TextMe SMS 安全漏洞 — TextMe SMS 6.5 Medium2025-04-03
CVE-2025-31795 WordPress plugin Shopify to WooCommerce Migration 安全漏洞 — Shopify to WooCommerce Migration 6.5 Medium2025-04-03
CVE-2025-31746 WordPress plugin Think201 Clients 安全漏洞 — Clients 6.4 Medium2025-04-03
CVE-2025-31736 WordPress plugin Rich Text Editor 安全漏洞 — Rich Text Editor 6.5 Medium2025-04-03
CVE-2025-31758 WordPress plugin Free Woocommerce Product Table View 安全漏洞 — Free Woocommerce Product Table View 6.5 Medium2025-04-03
CVE-2025-31739 WordPress plugin Minimalistic Event Manager 安全漏洞 — Minimalistic Event Manager 6.4 Medium2025-04-03
CVE-2025-31729 WordPress plugin WooTumblog 安全漏洞 — WooTumblog 6.5 Medium2025-04-03
CVE-2025-31581 WordPress plugin WP Video Playlist 安全漏洞 — WP Video Playlist 6.5 Medium2025-04-03
CVE-2025-31541 WordPress plugin TuriTop Booking System 安全漏洞 — TuriTop Booking System 6.5 Medium2025-04-03
CVE-2025-30916 WordPress plugin Residential Address Detection 安全漏洞 — Residential Address Detection 6.5 Medium2025-04-03
CVE-2025-30915 WordPress plugin Small Package Quotes – Worldwide Express Edition 安全漏洞 — Small Package Quotes – Worldwide Express Edition 6.5 Medium2025-04-03
CVE-2025-3063 WordPress plugin Shopper Approved Reviews 安全漏洞 — Shopper Approved Reviews 8.8 High2025-04-02
CVE-2024-13637 WordPress plugin Demo Awesome 安全漏洞 — Demo Awesome 6.5 Medium2025-04-02
CVE-2025-2779 WordPress plugin Insert Headers and Footers Code – HT Script 安全漏洞 — Insert Headers and Footers Code – HT Script 6.5 Medium2025-04-02
CVE-2025-31628 WordPress plugin Sliced Invoices 安全漏洞 — Sliced Invoices 5.3 Medium2025-04-01
CVE-2025-31580 WordPress plugin Ni WooCommerce Product Enquiry 安全漏洞 — Ni WooCommerce Product Enquiry 7.5 High2025-04-01
CVE-2025-31525 WordPress plugin WP Mobile Bottom Menu 安全漏洞 — WP Mobile Bottom Menu 4.3 Medium2025-04-01
CVE-2025-30853 WordPress plugin ShortPixel Adaptive Images 安全漏洞 — ShortPixel Adaptive Images 5.4 Medium2025-04-01

CWE-862(授权机制缺失) 是常见的弱点类别,本平台收录该类弱点关联的 5967 条 CVE 漏洞。