← Back
CWE-862

11,370 CVEs • Abstraction: Class • Likelihood of Exploit: High

Missing Authorization

The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

JSON object

Loading...

CVEs (11,370)

CVE
VENDORS
PRODUCTS
UPDATED
PUBLISHED
CVSS
-
-
Sep 9, 2026
Sep 9, 2026
N/A· v4
5.3 MEDIUM· v3
N/A· v2
The Masteriyo LMS WordPress plugin before 3.4.0 does not perform any authorization check before returning a course enrolment record over its REST API, allowing unauthenticated users to read any learner's enrolment statu...Show more
The Masteriyo LMS WordPress plugin before 3.4.0 does not perform any authorization check before returning a course enrolment record over its REST API, allowing unauthenticated users to read any learner's enrolment status, timestamps and course-progress data by walking sequential record identifiers. A related gap lets any enrolled user retrieve other learners' enrolment records as well.Show less
-
-
Sep 9, 2026
Sep 9, 2026
N/A· v4
4.3 MEDIUM· v3
N/A· v2
The WPLP Cookie Consent WordPress plugin before 4.4.2 does not have capability or nonce checks on some of its A/B testing actions, allowing any authenticated user, such as a subscriber, to overwrite the cookie banner co...Show more
The WPLP Cookie Consent WordPress plugin before 4.4.2 does not have capability or nonce checks on some of its A/B testing actions, allowing any authenticated user, such as a subscriber, to overwrite the cookie banner configuration shown to every visitor and to irreversibly reset the stored A/B test results.Show less
-
-
Sep 9, 2026
Sep 9, 2026
N/A· v4
5.3 MEDIUM· v3
N/A· v2
The WPLP Cookie Consent WordPress plugin before 4.4.2 does not have any authorisation or CSRF checks when storing visitor consent state, and the code that does so runs on every front-end page load, allowing unauthentica...Show more
The WPLP Cookie Consent WordPress plugin before 4.4.2 does not have any authorisation or CSRF checks when storing visitor consent state, and the code that does so runs on every front-end page load, allowing unauthenticated attackers to overwrite a site-wide option with arbitrary data.Show less
-
-
Sep 9, 2026
Sep 9, 2026
N/A· v4
4.3 MEDIUM· v3
N/A· v2
The WP Recipe Maker plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 10.8.0. This is due to the plugin not properly verifying that a user is authorized to perform an action...Show more
The WP Recipe Maker plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 10.8.0. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with contributor-level access and above, to take ownership of any admin-authored recipe by rewriting its post_author to the attacker's user ID, and unpublish it by overwriting its post_status with the contributor's draft or pending post status. This requires the default 'recipe_use_author' setting to be set to 'parent' for the ownership transfer to occur, though unpublishing remains possible regardless of this setting.Show less
-
-
Sep 9, 2026
Sep 9, 2026
N/A· v4
6.5 MEDIUM· v3
N/A· v2
The Ultimate Gift Cards for WooCommerce WordPress plugin before 3.2.10 does not verify that the user redeeming a gift card is its intended recipient, allowing any authenticated user, such as a subscriber, to redeem gift...Show more
The Ultimate Gift Cards for WooCommerce WordPress plugin before 3.2.10 does not verify that the user redeeming a gift card is its intended recipient, allowing any authenticated user, such as a subscriber, to redeem gift cards belonging to other users, zeroing their balance and crediting the value to themselves. In 3.2.9 an ownership check was added on one of the two affected redemption paths; the one that remains requires a companion Ultimate Gift Cards for WooCommerce WordPress plugin before 3.2.10 from the same vendor to be active.Show less
-
-
Sep 11, 2026
Sep 9, 2026
N/A· v4
4.3 MEDIUM· v3
N/A· v2
The Awesome Support plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 6.3.9. This is due to a missing capability check on the wpas_do_mr_deny_user() function, which unlike its...Show more
The Awesome Support plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 6.3.9. This is due to a missing capability check on the wpas_do_mr_deny_user() function, which unlike its counterpart wpas_do_mr_activate_user() does not enforce current_user_can('edit_users') or current_user_can('edit_user', $user_id), relying solely on a nonce that is not scoped to the target user. This makes it possible for authenticated attackers, with subscriber-level access and above, to set the mr_user_denied flag on any user account — including administrators — permanently blocking their moderated activation and dispatching a denial notification email to the victim.Show less
-
-
Sep 9, 2026
Sep 9, 2026
N/A· v4
5.3 MEDIUM· v3
N/A· v2
The WP Travel WordPress plugin before 12.0.2 does not verify that the requester is authorized to act on the booking targeted by one of its front-end payment-message handlers, allowing unauthenticated attackers to cancel...Show more
The WP Travel WordPress plugin before 12.0.2 does not verify that the requester is authorized to act on the booking targeted by one of its front-end payment-message handlers, allowing unauthenticated attackers to cancel the payment on any customer's booking.Show less
-
-
Sep 9, 2026
Sep 9, 2026
N/A· v4
5.4 MEDIUM· v3
N/A· v2
The Eventin – Event Calendar, Event Registration, Tickets & Booking (AI Powered) plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.1.17. This is due to the plugin not prop...Show more
The Eventin – Event Calendar, Event Registration, Tickets & Booking (AI Powered) plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.1.17. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to view, create, update, clone, and delete notification flow event automation workflows that should be restricted to administrators.Show less
1Tanium
1Comply
Sep 16, 2026
Sep 9, 2026
N/A· v4
6.5 MEDIUM· v3
N/A· v2
Tanium addressed an improper access controls vulnerability in Comply.
1Tanium
1Comply
Sep 16, 2026
Sep 9, 2026
N/A· v4
7.1 HIGH· v3
N/A· v2
Tanium addressed an improper access controls vulnerability in Comply.
1Tanium
1Comply
Sep 16, 2026
Sep 9, 2026
N/A· v4
5.4 MEDIUM· v3
N/A· v2
Tanium addressed an improper access controls vulnerability in Comply.
1Tanium
1Comply
Sep 16, 2026
Sep 9, 2026
N/A· v4
5.4 MEDIUM· v3
N/A· v2
Tanium addressed an improper access controls vulnerability in Comply.
1Tanium
1Comply
Sep 16, 2026
Sep 9, 2026
N/A· v4
8.1 HIGH· v3
N/A· v2
Tanium addressed an improper access controls vulnerability in Comply.
-
-
Sep 9, 2026
Sep 9, 2026
N/A· v4
5.3 MEDIUM· v3
N/A· v2
The WP Event Solution (Eventin) plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 4.1.22 via the create_item() handler for the /wp-json/eventin/v2/orders REST endpoint. The end...Show more
The WP Event Solution (Eventin) plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 4.1.22 via the create_item() handler for the /wp-json/eventin/v2/orders REST endpoint. The endpoint's create_item_permissions_check() function only verifies a wp_rest nonce (which is leaked to every visitor through the etn-public script's localized_data_obj on every frontend page) and accepts a user-supplied 'status' value in prepare_item_for_database() with no whitelist validation. This makes it possible for unauthenticated attackers to create etn-order posts with status='completed' that are counted as sold by etn_get_sold_tickets_by_event(); because the auto-cleanup wp_schedule_single_event() in create_item() only fires for status='pending' orders, the forged completed orders persist indefinitely and exhaust ticket inventory.Show less
1Google
1Chrome
Sep 9, 2026
Sep 9, 2026
N/A· v4
6.5 MEDIUM· v3
N/A· v2
Missing authorization in DOM in Google Chrome prior to 153.0.8010.36 allowed a remote attacker to potentially leak sensitive information via a crafted HTML page. (Chromium security severity: Low)
1Google
1Chrome
Sep 9, 2026
Sep 9, 2026
N/A· v4
4.3 MEDIUM· v3
N/A· v2
Missing authorization in FedCM in Google Chrome prior to 153.0.8010.36 allowed a remote attacker to bypass web origin policy via a crafted HTML page. (Chromium security severity: Medium)
1Google
1Chrome
Sep 9, 2026
Sep 9, 2026
N/A· v4
3.1 LOW· v3
N/A· v2
Missing authorization in FileSystem in Google Chrome prior to 153.0.8010.36 allowed a remote attacker who had compromised the renderer process to obtain cross-origin data via a crafted HTML page. (Chromium security sever...Show more
Missing authorization in FileSystem in Google Chrome prior to 153.0.8010.36 allowed a remote attacker who had compromised the renderer process to obtain cross-origin data via a crafted HTML page. (Chromium security severity: Medium)Show less
1Google
1Chrome
Sep 11, 2026
Sep 9, 2026
N/A· v4
8.1 HIGH· v3
N/A· v2
Missing authorization in SiteIsolation in Google Chrome prior to 153.0.8010.36 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page. (Chromium security sever...Show more
Missing authorization in SiteIsolation in Google Chrome prior to 153.0.8010.36 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page. (Chromium security severity: Medium)Show less
1Google
1Chrome
Sep 9, 2026
Sep 9, 2026
N/A· v4
5.3 MEDIUM· v3
N/A· v2
Missing authorization in Contacts in Google Chrome prior to 153.0.8010.36 allowed a remote attacker who had compromised the renderer process and leveraged social engineering to potentially obtain sensitive information vi...Show more
Missing authorization in Contacts in Google Chrome prior to 153.0.8010.36 allowed a remote attacker who had compromised the renderer process and leveraged social engineering to potentially obtain sensitive information via a crafted HTML page. (Chromium security severity: Low)Show less
1Google
1Chrome
Sep 11, 2026
Sep 9, 2026
N/A· v4
6.5 MEDIUM· v3
N/A· v2
Missing authorization in FileSystem in Google Chrome prior to 153.0.8010.36 allowed a remote attacker to bypass system access restrictions via a crafted HTML page. (Chromium security severity: Medium)