CVE-2026-130730
NocoDB before 2026.10.1 contains an authentication bypass vulnerability that allows OAuth token holders to act as full sessions because OAut
CVSS
8.7
Alto
EPSS
—
KEV
—
Exploit Today
0
0-100
Publicado: 18 nov 2026 · Última mod.: 18 nov 2026 · CWE-287
Sin historial EPSS suficiente todavía.
NocoDB before 2026.10.1 contains an authentication bypass vulnerability that allows OAuth token holders to act as full sessions because OAuth access tokens are signed with the instance JWT secret. Attackers can present a narrowly scoped OAuth token to the session strategy, short-lived-token exchange, or NocoSocket handshake to gain the granting user's full privileges.
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2026-631899.8 CRÍ—
———Dialoqbase is an application for creating chatbots. Prior to 1.11.5, the unauthenticated GET /api/v1/view/* route in server/src/routes/api/v1/view/root.ts resolves its attacker-controlled wildcard path without normalization or containment, allowing traversal outside the intended uploads directory and arbitrary server file reads. Reading environment files can disclose DB_SECRET_KEY, the application’s JWT signing key, which permits forged administrator tokens and takeover of bots, conversations, integrations, and stored third-party credentials. This issue is fixed in version 1.11.5.31mCVE-2026-1108119.8 CRÍ—
———The Trust Payments Gateway for WooCommerce (JavaScript Library) plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 1.3.8. The vulnerability exists because the `new_customer_account()` function stores the raw return value of `wp_create_user()` — including a `WP_Error` object returned on username collision — into the order's `tp_userid` post meta before the `is_wp_error()` guard is evaluated; the `add_customer_details_to_thankyou_page()` callback subsequently reads that meta and casts it with `(int)`, causing PHP to coerce any object to integer `1`, after which `wp_set_current_user(1)` and `wp_set_auth_cookie(1)` are called unconditionally. This makes it possible for unauthenticated attackers to authenticate as WordPress user ID 1 — the bootstrap site administrator or, on multisite, a network super-admin — by supplying the `new_username` parameter matching any existing login during checkout and visiting the resulting thank-you page. Exploitation requires the Trust Payments gateway to be active and the attacker to complete a paid order on their own account; the ID 1 administrator username is additionally enumerable via standard WordPress user enumeration techniques.3hCVE-2026-1100099.8 CRÍ—
———The Unzer Payments plugin for WordPress is vulnerable to Authentication Bypass leading to Account Takeover in all versions up to, and including, 2.2.1. The vulnerability exists because the Google Pay Express Checkout endpoint (`/?wc-api=google_pay_express`), handled by `startCheckoutDataWithNormalizedCustomerData`, accepts an attacker-controlled `paymentData.email` value and passes it to `createOrGetGuestCustomer()`, which resolves the submitted email to any existing WordPress user via `get_user_by('email', ...)` and then calls `wp_set_current_user()` and `wp_set_auth_cookie()` for the resolved user ID without verifying ownership of the email address, a password, a nonce, an authentication token, or any proof of payment from the payment provider. This makes it possible for unauthenticated attackers to log in as any existing WordPress user — including administrators — by submitting that user's known email address, receiving valid `wordpress_logged_in_*` session cookies for the targeted account and achieving full site takeover. The endpoint is entirely unprotected with no capability check, nonce validation, or payment-provider signature verification applied, and administrator email addresses are frequently discoverable via the WordPress REST API user enumeration endpoint (`/wp-json/wp/v2/users`), author archive pages, Gravatar lookups, or site contact footers.5hCVE-2026-1076447.4 ALT—
———The Bizuno Accounting – ERP/Accounting/CRM (for WordPress) plugin for WordPress is vulnerable to Authentication Bypass via Password Reset Token Disclosure in all versions up to, and including, 7.4.5 via the `bizUser` parameter of the `validateReset()` function on the `portal/api/lostPW` endpoint. This is due to `portalCtl::goAPI()` failing to call `loadBusinessCache()` before invoking the handler, which causes `isMailConfigured()` to read an empty business cache and return false regardless of the site's actual mail configuration, causing the fully-qualified reset URL — containing the victim's live reset UUID and numeric user ID — to be embedded directly in the HTML response rather than delivered by email. This makes it possible for unauthenticated attackers to obtain a valid password-reset token for any Bizuno account, including administrators, directly from the HTTP response and submit it to the `portal/api/lostVal` endpoint to rewrite the victim's password and achieve full account takeover. The administrator email address required to initiate the reset is frequently exposed by the plugin's own login error messages and the public `/bizuno/` portal page, making exploitation trivial against most installations.4hCVE-2026-128981——
——0** 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.9hCVE-2026-19399——
——0Improper Authentication and Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in ASUS Router firmware allow an unauthenticated nearby user to perform file operations or read files in an unintended directory via crafted HTTP requests during an active user session.
Refer to the '
Security Update for ASUS Router Firmware ' section on the ASUS Security Advisory for more information.17h