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

目标: 1000 元 · 已筹: 1325

100%

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

CWE-862 授权机制缺失 类弱点 5949 条 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-12041 WordPress plugin ERI File Library 安全漏洞 — ERI File Library 5.3 Medium2025-10-31
CVE-2025-12175 WordPress plugin The Events Calendar 安全漏洞 — The Events Calendar 4.3 Medium2025-10-31
CVE-2025-11975 WordPress plugin FuseWP 安全漏洞 — FuseWP – WordPress User Sync to Email List & Marketing Automation (Mailchimp, Constant Contact, ActiveCampaign etc.) 4.3 Medium2025-10-31
CVE-2023-7317 Nagios XI 安全漏洞 — XI 8.8AIHighAI2025-10-30
CVE-2013-10072 Nagios XI 安全漏洞 — XI 7.1AIHighAI2025-10-30
CVE-2024-13994 Nagios XI 安全漏洞 — XI 8.8AIHighAI2025-10-30
CVE-2025-62712 JumpServer 安全漏洞 — jumpserver 9.6 Critical2025-10-30
CVE-2025-11881 WordPress plugin AppPresser 安全漏洞 — AppPresser – Mobile App Framework 5.3 Medium2025-10-30
CVE-2025-10008 WordPress plugin Weglot 安全漏洞 — Translate WordPress with Weglot – Multilingual AI Translation 5.3 Medium2025-10-30
CVE-2025-9954 Drupal Acquia DAM 安全漏洞 — Acquia DAM 7.5AIHighAI2025-10-29
CVE-2025-11587 WordPress plugin Call Now Button 安全漏洞 — Call Now Button – The #1 Click to Call Button for WordPress 4.3 Medium2025-10-29
CVE-2025-11632 WordPress plugin Call Now Button 安全漏洞 — Call Now Button – The #1 Click to Call Button for WordPress 4.3 Medium2025-10-29
CVE-2025-64285 Wordpress plugin Premmerce Wholesale Pricing for WooCommerce 安全漏洞 — Premmerce Wholesale Pricing for WooCommerce 5.4 Medium2025-10-29
CVE-2025-64234 WordPress plugin Evergreen Content Poster 安全漏洞 — Evergreen Content Poster 4.3 Medium2025-10-29
CVE-2025-64229 WordPress plugin Client Invoicing by Sprout Invoices 安全漏洞 — Client Invoicing by Sprout Invoices 4.3 Medium2025-10-29
CVE-2025-64219 WordPress plugin Business Directory 安全漏洞 — Business Directory 4.3 Medium2025-10-29
CVE-2025-64212 WordPress plugin MasterStudy LMS Pro 安全漏洞 — MasterStudy LMS Pro 5.4 Medium2025-10-29
CVE-2025-64210 WordPress plugin Masterstudy Elementor Widgets 安全漏洞 — Masterstudy Elementor Widgets 5.4 Medium2025-10-29
CVE-2025-64211 WordPress plugin Masterstudy Elementor Widgets 安全漏洞 — Masterstudy Elementor Widgets 5.3 Medium2025-10-29
CVE-2025-64199 WordPress plugin wpresidence 安全漏洞 — wpresidence 5.3 Medium2025-10-29
CVE-2025-58711 WordPress plugin Blog Designer PRO 安全漏洞 — Blog Designer PRO 5.3 Medium2025-10-29
CVE-2025-11702 GitLab 安全漏洞 — GitLab 8.5 High2025-10-29
CVE-2025-11705 WordPress plugin Anti-Malware Security and Brute-Force Firewall 安全漏洞 — Anti-Malware Security and Brute-Force Firewall 6.5 Medium2025-10-29
CVE-2025-64296 WordPress plugin Facebook for WooCommerce 安全漏洞 — Facebook for WooCommerce 5.3 Medium2025-10-29
CVE-2025-59461 SICK AG TLOC100-100 安全漏洞 — TLOC100-100 all Firmware versions 7.6 High2025-10-27
CVE-2025-62980 WordPress plugin Persian Admnin Fonts 安全漏洞 — Persian Admnin Fonts 5.4 Medium2025-10-27
CVE-2025-62978 WordPress plugin KiotViet Sync 安全漏洞 — KiotViet Sync 4.3 Medium2025-10-27
CVE-2025-62976 WordPress plugin Sendle Shipping 安全漏洞 — Sendle Shipping 5.3 Medium2025-10-27
CVE-2025-62977 WordPress plugin SEO合集(支持百度/Google/Bing/头条推送) 安全漏洞 — 百度站长SEO合集(支持百度/神马/Bing/头条推送) 5.3 Medium2025-10-27
CVE-2025-62973 WordPress plugin BuddyForms 安全漏洞 — BuddyForms 5.3 Medium2025-10-27

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