Auth & access CVEs.
Published CVEs classified as auth & access, ranked by exploit odds.
-
CVE-2026-130711
NocoDB before 2026.09.0 contains an authorization bypass vulnerability in extract-ids.middleware.ts that allows authenticated users to resolve roles against another base by supplying an MCP token id in the query string. Attackers with Viewer access on one base can mint an MCP token and pass its id to read another base's metadata, including table lists and member email addresses.
-
CVE-2026-130712
NocoDB before 2026.08.1 contains an authorization bypass vulnerability that allows authenticated Creators to access another tenant's external database by reusing a victim source id when adding a source. Because NcConnectionMgrv2 caches connections by bare source id, attackers can reflect the victim's cached database schema and read, update, and insert records through their own base models.
-
CVE-2026-130703
NocoDB before 2026.10.0 contains an information disclosure vulnerability that allows unauthenticated attackers to read hidden columns by supplying comma-separated group-by column lists. Attackers with a shared view link can pair a visible and hidden column to bypass restrictSharedViewColumnReferences and retrieve hidden values tied to individual rows.
-
CVE-2026-130704
NocoDB before 2026.10.0 contains an improper access control vulnerability that allows Creator-role users to attach NocoDB's internal database by supplying is_meta and is_local flags. Attackers can create sources or bases with these flags to expose user, token and integration tables, then read and modify records including user roles.
-
CVE-2026-130705
NocoDB before 2026.10.1 contains an information disclosure vulnerability that allows unauthenticated shared view link holders to read hidden columns by grouping on physical column names. Attackers can supply a hidden column's physical name or the unchecked sub-group parameter to the public group-by endpoint to reveal hidden values, counts, and column existence.
-
CVE-2026-130695
NocoDB before 2026.10.1 contains an authentication bypass vulnerability that allows holders of revoked OAuth access tokens to authenticate as first-party sessions by presenting them through the session header. Attackers can bypass revocation, client-existence, route allowlist and granted_resources scope checks to modify victim profiles, upload to storage, and force global sign-outs.
-
CVE-2026-130696
NocoDB before 2026.10.1 contains a credential exposure vulnerability in the connection-test endpoint that allows authorized integration users to redirect stored credentials by overriding connection host, port, and user fields. Attackers can point the test at a server they control to capture offline-crackable PostgreSQL md5 or MySQL handshakes and recover the stored database password.
-
CVE-2026-130690
NocoDB before 2026.10.1 contains an incorrect authorization vulnerability that allows organization Creators to reach routes restricted to other roles because the aclFn middleware never enforced allowedRoles. Attackers can generate a super admin password reset link via org-users endpoints to take over the instance, or read and modify SSO client secrets.
-
CVE-2026-130693
NocoDB from 0.253.0 before 2026.09.1 contains an incorrect authorization vulnerability in baseUserDelete that allows base Creators to remove higher-privileged Owners due to a broken role power comparison. Attackers holding the Creator role can remove other Owners of a base, since getProjectRolePower returns -1 for the target and never refuses the request.
-
CVE-2026-130677
Craft CMS from 5.0.0 before 5.11.4 contains an improper session management vulnerability that fails to invalidate existing sessions when 2FA is enabled and allows disabling 2FA without re-authentication. Attackers holding a hijacked or stale session can retain full account access and silently remove 2FA without the password, authenticator code, or recovery code.
-
CVE-2026-130671
Parse Server before 8.6.119 and 9.x before 9.10.8-alpha.3 contains a missing authorization vulnerability that allows LiveQuery clients without the master key to subscribe to installation and internal classes. Attackers can receive installation IDs and device tokens of other devices when these classes are in liveQuery.classNames, then modify those installations to redirect push notifications.
-
CVE-2026-130672
Craft CMS from 5.0.0 before 5.11.5 contains a missing authorization vulnerability in ChartsController::actionGetNewUsersData() that lacks a viewUsers permission check. Authenticated control panel users can POST to the charts/get-new-users-data action to read aggregate user-registration time series and totals for the site or any user group.
-
CVE-2026-130653
ImageMagick before 7.1.2-35 contains a policy bypass vulnerability that allows attackers to read from disallowed paths due to a missing policy check when decoding MPC files. Attackers can supply crafted MPC files that reference restricted locations to access files the configured security policy should block.
-
CVE-2026-130034
The Nexter Blocks – Gutenberg Blocks, Page Builder & AI Website Builder plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 5.0.10 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 create, modify, and delete entries in the site-wide global button-preset store, and inject arbitrary CSS rules into the generated plus-button-presets stylesheet served to all site visitors.
-
CVE-2026-119634
The User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 4.3.14 via the `draft_post()` function. This is due to the function storing the `post_content` parameter via `wp_insert_post()` without the protected-shortcode allow-list check that was introduced in 4.3.14 for the sibling `submit_post()` handler — a gap that `wp_kses` filtering does not close, as it strips only HTML tags while leaving shortcode text such as `[wpuf-registration role="editor"]` intact. This makes it possible for authenticated attackers, with Author-level access and above, to embed a registration shortcode in a post and cause any site visitor who subsequently registers through the rendered form to receive Editor-level access. The render-time `wpuf_modify_shortcodes` filter that is designed to neutralize protected shortcodes provides no protection here because posts created via the `wpuf_draft_post` AJAX endpoint carry no `_edit_last` post meta, causing the filter to return the content unchanged and allowing the shortcode to render and execute fully.
-
CVE-2026-11602
The FS Poster - WordPress Social media Auto Poster & Scheduler [Facebook, Instagram, Twitter, Pinterest] plugin for WordPress is vulnerable to missing authorization to Unauthorized Social App Data Modification in all versions up to, and including, 8.0.1 This is due to missing authentication, nonce, and capability checks in the `standardFSApp()` function, which is registered on the `wp` action hook and executes on every frontend page load without any login or permission verification. This makes it possible for unauthenticated attackers to insert arbitrary social network app records into the database, or overwrite the OAuth `client_id` and `client_secret` of existing social network connections, by supplying attacker-controlled values via the `fsp_app_redirect` and `app` GET parameters. An attacker can target a specific existing social app record for credential overwrite by supplying matching `social_network` and `slug` values, requiring no knowledge of internal record IDs, which disrupts scheduled social media posts and forces administrators to re-authenticate their connected accounts.
-
CVE-2026-119220
The Dokan: AI Powered WooCommerce Multivendor Marketplace Solution – Build Your Own Amazon, eBay, Etsy plugin for WordPress is vulnerable to Authorization Bypass in all versions up to, and including, 5.3.3. The vulnerability exists because the `matches_mcp_endpoint()` function applies an unanchored regular expression (`#/(?:woocommerce|dokan)/mcp(?:/|$)#`) against the entire `REQUEST_URI` including the query string, meaning any request that contains the literal substring `/dokan/mcp/` or `/woocommerce/mcp/` anywhere in its URI — including inside a query parameter value — is incorrectly treated as a trusted internal MCP context, causing `scope_product_permissions()` to unconditionally return `true` on WooCommerce's `woocommerce_rest_check_permissions` filter regardless of whether the caller is authenticated. This makes it possible for unauthenticated attackers to read full authenticated WooCommerce REST product records for any published product — including private underscore-prefixed meta, purchase notes, downloadable file URLs for paid digital products, catalog-hidden products, and edit-context representations — across the `/wc/v1`, `/wc/v2`, `/wc/v3`, and `/wc-analytics` REST namespaces. The bypass is triggered by appending a query parameter whose value contains the literal string `/dokan/mcp/` to any WooCommerce REST product endpoint (e.g., `/wp-json/wc/v3/products/{id}?x=/dokan/mcp/`); note that percent-encoding the slashes prevents the bypass, as the unencoded literal slash characters are required for the regex to match.
-
CVE-2026-132069
MISP (Malware Information Sharing Platform) contains an authorization bypass in the SharingGroup model's captureSGExisting method. The authorization check used a logical AND condition that effectively exempted users with the sync permission (perm_sync) from the membership verification. Specifically, the original condition 'if (!checkIfAuthorised(...) && !perm_sync) return false' meant that any user holding the sync role would pass the check regardless of whether they were actually a member of the target sharing group. A sync user who knows or can discover the UUID of a non-local sharing group could exploit this flaw through the /sharing_groups/add endpoint or by embedding a SharingGroup object in pushed sync data. The attacker could rewrite the sharing group record to add their own organisation as a member or insert an all_orgs server entry for their MISP instance, thereby gaining read access to all events contained in that group. This exposes threat intelligence data that was intended to be restricted to the group's legitimate members. The vulnerability requires an authenticated account with the sync role and knowledge of a valid sharing group UUID. No user interaction is required. The impact is unauthorized disclosure of shared threat intelligence events and limited integrity modification of the sharing group record.
-
CVE-2026-1214
The BuddyPress plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 14.5.0. This is due to missing authorization checks in the `bp_nouveau_ajax_get_single_activity_content` AJAX handler. The function only verifies a nonce that is publicly exposed to any visitor who loads a BuddyPress page, but does not call `bp_activity_user_can_read()` to verify the user has permission to view the activity. This makes it possible for unauthenticated attackers to read private group activity content by iterating activity IDs.
-
CVE-2026-58320
Missing Authorization vulnerability in the Apache Iggy server. The system snapshot command (GetSnapshot on the binary transports and POST /snapshot on HTTP) checked only that the caller was logged in, not the read_servers or manage_servers permission. Any authenticated user, including a user with no permissions, could download a diagnostic archive with the server log files, the host process list, a file system listing and the runtime server configuration. The runtime configuration contains the HTTP JWT signing secret and the message encryption key when they are set in the configuration. If HTTP is enabled, the user could use the signing secret to create tokens for any account, including root. This issue affects Apache Iggy: before 0.9.0. Users are recommended to upgrade to version 0.10.0, which fixes the issue.
-
CVE-2026-129705
In Eclipse Mosquitto versions 2.1.0 to 2.1.2, a broker with a listener that is configured to use the PROXY protocol v2 is vulnerable to an untrusted proxy providing details that cause the broker to accept fake SSL information. This can be mitigated by following the documented requirements for PROXY listeners: It is very important that only trusted proxies are allowed to connect to any listener using the PROXY protocol, and that clients are not allowed to connect to the listener at all.
-
CVE-2026-123343
The BlockArt Blocks – Gutenberg Blocks, Page Builder Blocks ,WordPress Block Plugin, Sections & Template Library plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.4.3. 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 view the title, excerpt, and full content of other users' draft, pending, and private posts, exposing that content to unauthenticated visitors on the published permalink. This is exploitable by an Author-level user because WordPress's wp_filter_post_kses preserves block-comment JSON in HTML comments, allowing the malicious queryArgs and query[post_status] attributes to survive post saving and execute on every unauthenticated request to the published URL. Exploitation by attackers with contributor-level access and above requires that attacker only needs to see the data themselves (not expose it to unauthenticated visitors) — satisfied by viewing their own preview URL. On a default installation, where that is not configured, the vulnerability requires attackers with author-level access and above.
-
CVE-2026-110513
Insufficient Session Expiration vulnerability in the Apache Iggy server HTTP transport. A self-issued JSON Web Token (JWT) identified the user only by numeric user ID, and a new user takes the lowest free ID. After an administrator deleted a user, that user's unexpired token, or a token refreshed from it while the ID was free, authenticated as the next account created with that ID and had that account's permissions. Only deployments with HTTP enabled are affected. This issue affects Apache Iggy: through 0.9.0. Users are recommended to upgrade to version 0.10.0, which fixes the issue.
-
CVE-2026-113497
A low-privileged remote attacker can change the password of arbitrary users using the REST API, including administrative accounts. By changing the administrator password, an attacker can obtain full administrative access to the device and modify all configuration settings.
-
CVE-2026-128981
** UNSUPPORTED WHEN ASSIGNED ** Improper Authentication in Apache SeaTunnel Web 1.0.2 allows a user whose account has been disabled to authenticate with valid credentials and obtain a new login token. The login query does not check the account status, so disabling an account does not prevent new logins or access to protected APIs using the newly issued token. This issue requires valid credentials for the disabled account; it is not a credential-free authentication bypass. Apache SeaTunnel Web is no longer maintained. The affected 1.0.2 release does not contain the account-status check added to the main branch in pull request #264. There is no maintained fixed release. Users should discontinue use of this unsupported component. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
A list of CVEs whose flaw type is auth & access, sorted by how likely they are to be exploited (EPSS). Classification uses the CWE weakness id where present, and a small local model otherwise.