CVE Vulnerability Catalog

In charger, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained the System privilege. User interaction is not needed for exploitation.

In the wlan AP driver, there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to local privilege escalation if a malicious actor has already obtained System privileges. User interaction is not required for exploitation.

In gnss service, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained the System privilege. User interaction is not needed for exploitation.

In gnss service, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained the System privilege. User interaction is not needed for exploitation.

In apusys, there is a possible memory corruption due to use after free. This could lead to local escalation of privilege if a malicious actor has already obtained System privilege, with no user interaction needed.

In pda, there is a possible escalation of privilege due to use after free. This could lead to local escalation of privilege if a malicious actor has already obtained System privilege, with no user interaction needed.

In the wlan AP driver, there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained System privilege. User interaction is not needed for exploitation.

In wlan STA driver, there is a possible out of bounds read due to a race condition. This could lead to local information disclosure with User execution privileges needed. User interaction is not needed for exploitation.

In the wlan AP driver, there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to local privilege escalation if a malicious actor has already obtained System privileges. No user interaction is required for exploitation.

In the wlan AP driver, there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to local privilege escalation if a malicious actor has already obtained System privileges. No user interaction is required for exploitation.

In the wlan AP driver, there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained System privilege. User interaction is not needed for exploitation.

In the wlan AP driver, there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained System privilege. User interaction is not needed for exploitation.

In the wlan AP driver, there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained System privilege (when OceReducedNeighborReport is disabled). User interaction is not needed for exploitation.

In the WLAN AP driver, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained the System privilege (when OceReducedNeighborReport is disabled). User interaction is not needed for exploitation.

In the wlan AP driver, there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained System privileges.

The service employed by Everything, running as SYSTEM, communicates with the lower privileged Everything GUI via a named pipe. The named pipe has a NULL DACL and thus provides all users full permission over it; leading to potential Service Denial Of Service or Privilege escalation (only if chained with other elements) for a local low privilege user.

The Centangle-Team plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to and including 1.0.0 due to missing or incorrect nonce validation on a function. This allows unauthenticated attackers to modify plugin settings via a forged request if they can trick a site administrator into clicking a link. Additionally, insufficient input sanitization and output escaping on the cai_name_color parameter allows injection of arbitrary web scripts that execute when a user accesses an injected page.

The Visit Counter plugin for WordPress is vulnerable to Cross-Site Request Forgery in version 1.0. This is due to missing or incorrect nonce validation on the widgets.php page. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

The Pagerank Tools plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Cross-Site Request Forgery in all versions up to, and including, 1.1.5. This is due to missing nonce validation on the pr_save_settings() function and insufficient input sanitization. This makes it possible for unauthenticated attackers to inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

The MapMap plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to and including 1.1 due to missing or incorrect nonce validation on the admin_shortcode_submit, admin_configuration_submit, and admin_shortcode_delete functions. This allows unauthenticated attackers to update plugin settings and inject malicious web scripts via a forged request if they can trick a site administrator into clicking a link.