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

目标: 1000 元 · 已筹: 1336

100%

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

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

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

MITRE CWE 官方描述
CWE:CWE-862 Missing Authorization(缺失授权) 英文:当主体尝试访问资源或执行操作时,产品未执行授权检查。
常见影响 (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.
缓解措施 (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.
代码示例 (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-34171 CasaOS 安全漏洞 — CasaOS - - 2026-01-03
CVE-2026-21429 emlog 安全漏洞 — emlog 3.8 - 2026-01-02
CVE-2025-14047 WordPress plugin WP User Frontend 安全漏洞 — User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership & User Registration 5.3 Medium 2026-01-02
CVE-2025-15406 PHPGurukul Online Course Registration 安全漏洞 — Online Course Registration 6.3 Medium 2026-01-01
CVE-2025-14428 WordPress plugin My Sticky Elements 安全漏洞 — All-in-one Sticky Floating Contact Form, Call, Click to Chat, and 50+ Social Icon Tabs – My Sticky Elements 4.3 Medium 2026-01-01
CVE-2025-66144 WordPress plugin Worker for Elementor 安全漏洞 — Worker for Elementor 5.4 Medium 2025-12-31
CVE-2025-66145 WordPress plugin Worker for WPBakery 安全漏洞 — Worker for WPBakery 5.4 Medium 2025-12-31
CVE-2025-66146 WordPress plugin Logger for Elementor 安全漏洞 — Logger for Elementor 5.4 Medium 2025-12-31
CVE-2025-66148 WordPress plugin Conformer for Elementor 安全漏洞 — Conformer for Elementor 5.4 Medium 2025-12-31
CVE-2025-66149 WordPress plugin UnGrabber 安全漏洞 — UnGrabber 5.4 Medium 2025-12-31
CVE-2025-66150 WordPress plugin Appender 安全漏洞 — Appender 5.4 Medium 2025-12-31
CVE-2025-66151 WordPress plugin Countdowner for Elementor 安全漏洞 — Countdowner for Elementor 5.4 Medium 2025-12-31
CVE-2025-66152 WordPress plugin Criptopayer for Elementor 安全漏洞 — Criptopayer for Elementor 5.4 Medium 2025-12-31
CVE-2025-66153 WordPress plugin Headinger for Elementor 安全漏洞 — Headinger for Elementor 5.4 Medium 2025-12-31
CVE-2025-66154 WordPress plugin Couponer for Elementor 安全漏洞 — Couponer for Elementor 5.4 Medium 2025-12-31
CVE-2025-66155 WordPress plugin Questionar for Elementor 安全漏洞 — Questionar for Elementor 5.4 Medium 2025-12-31
CVE-2025-66156 WordPress plugin Watcher for Elementor 安全漏洞 — Watcher for Elementor 5.4 Medium 2025-12-31
CVE-2025-66157 WordPress plugin Slider for Elementor 安全漏洞 — Sliper for Elementor 5.4 Medium 2025-12-31
CVE-2025-66158 WordPress plugin Gmaper for Elementor 安全漏洞 — Gmaper for Elementor 5.4 Medium 2025-12-31
CVE-2025-66159 WordPress plugin Walker for Elementor 安全漏洞 — Walker for Elementor 5.4 Medium 2025-12-31
CVE-2025-66160 WordPress plugin Select Graphist for Elementor Graphist for Elementor 安全漏洞 — Select Graphist for Elementor Graphist for Elementor 5.4 Medium 2025-12-31
CVE-2025-62874 WordPress plugin AnyComment 安全漏洞 — AnyComment 4.3 Medium 2025-12-31
CVE-2025-62099 WordPress plugin Signature Add-On for Gravity Forms 安全漏洞 — Signature Add-On for Gravity Forms 4.3 Medium 2025-12-31
CVE-2025-63038 WordPress plugin WP Custom Admin Interface 安全漏洞 — WP Custom Admin Interface 4.3 Medium 2025-12-31
CVE-2025-62078 WordPress plugin Easy Upload Files During Checkout 安全漏洞 — Easy Upload Files During Checkout 4.3 Medium 2025-12-31
CVE-2025-49339 WordPress plugin Direct Payments WP 安全漏洞 — Direct Payments WP 4.3 Medium 2025-12-31
CVE-2025-62115 WordPress plugin Hide Plugins 安全漏洞 — Hide Plugins 4.3 Medium 2025-12-31
CVE-2025-62087 WordPress plugin Sticky Notes for WP Dashboard 安全漏洞 — Sticky Notes for WP Dashboard 4.3 Medium 2025-12-31
CVE-2025-49356 WordPress plugin Orders Chat for WooCommerce 安全漏洞 — Orders Chat for WooCommerce 4.3 Medium 2025-12-31
CVE-2025-63004 WordPress plugin All in One Accessibility 安全漏洞 — All in One Accessibility 4.3 Medium 2025-12-31

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