Apache Roller 6.1.5 contains an incorrect authorization vulnerability in its OAuth 1.0a authorization endpoint. This flaw allows an unauthenticated remote attacker who knows an outstanding request token for a configured site-wide consumer to bind that token to any user account, including administrators, by submitting an unsigned authorization request. The vulnerability arises because the endpoint derives the authorizing identity from a request-supplied value instead of the authenticated session. Only installations with an OAuth 1.0a site-wide consumer configured are affected. Upgrading to Apache Roller 6.1.6 or later mitigates this issue by binding authorization to the logged-in session.
Capgo.app versions prior to 12.127.5 contain an authorization flaw in the PATCH /private/role_bindings/:binding_id endpoint. This flaw allows an authenticated user with the org_admin role (rank 90) to demote an org_super_admin (rank 95) to a lower-privileged role, potentially removing all super administrators from an organization. The issue arises because the endpoint does not verify the current role's rank before allowing the change, and a database trigger that prevents deleting the last super admin does not apply to updates. The vulnerability is fixed in version 12.127.5.
CVE-2026-100616 is an authorization vulnerability in capgo.app, an over-the-air update platform for Capacitor apps. The flaw allows an organization admin with the org.update_settings permission to update the entire row in the public.orgs table, including the internal billing pointer customer_id, by bypassing the official update endpoint restrictions. This can corrupt or nullify the Stripe customer pointer, causing billing and plan checks to fail and resulting in the organization being treated as unpaid or without a plan. No patched version is currently available.
capgo.app is an over-the-air (OTA) update platform for Capacitor apps. In all versions up to and including the current release (no patch available at time of publication), the `transfer_app()` database function transfers an app, its channels, versions and related records to a destination organization without deleting or revalidating existing rows in `channel_permission_overrides`. As a result, a user who legitimately held a channel permission override while a member of the source organization retains that override after the transfer, even though they have no membership and no RBAC binding in the destination organization. Using their own authenticated JWT against the PostgREST API, such a former member can modify the destination-owned channel to point at a different bundle, causing the /updates endpoint to serve an attacker-selected application version to devices. The previously proposed fix for GHSA-626c-p6fq-3whq (PR #3093), which validates organization membership when an override is created or updated, does not remove overrides that became stale as a result of an app transfer.
Actual is a local-first personal finance tool. Prior to 26.7.0, Actual Sync Server's CORS proxy is intended to let authenticated users fetch resources only from repositories listed in the official plugin allowlist. When `ACTUAL_GITHUB_TOKEN` is configured, the proxy automatically attaches the server's GitHub token to GitHub requests. The GitHub API allowlist check uses a raw `startsWith()` prefix test for `/repos/{owner}/{repo}` without requiring a path boundary after the repository name. If an allowlisted public plugin repository is `https://github.com/acme/plugin`, the proxy also accepts GitHub API URLs. Those URLs are outside the allowlisted repository but still pass because their API path starts with `/repos/acme/plugin`. The proxy then forwards the request with the server's `ACTUAL_GITHUB_TOKEN`, allowing any authenticated Actual user to read private GitHub resources reachable by that token. Version 26.7.0 fixes the issue.
CVE-2026-67411 is an incorrect authorization vulnerability in rabbitmq-server affecting native MQTT and MQTT over WebSocket when used behind a trusted PROXY Protocol frontend. Versions from 3.13.0 up to but not including 3.13.18, 4.0.0 up to 4.0.23, 4.1.0 up to 4.1.14, 4.2.0 up to 4.2.9, and 4.3.0 up to 4.3.3 are affected. The flaw allows an attacker with valid credentials for a loopback-restricted account to bypass source-address restrictions due to loss of the proxy-derived client address before authentication checks. Password authentication is still required. The issue has been fixed in the specified later versions.
CVE-2026-93643 is a critical path traversal vulnerability in Zimbra Collaboration Suite (ZCS) affecting versions prior to 10.1.21. It allows an unauthenticated remote attacker with access to a supported public Briefcase document to abuse unsigned save fields, enabling path-traversal writes and command execution as the zimbra user. The vulnerability arises when OnlyOffice/Document Editing is enabled. The CVSS 3.1 score is 9.8, indicating high impact on confidentiality, integrity, and availability.
The MasterStudy LMS WordPress plugin from 1.9 before 3.7.50 does not verify that a course a member asks to enrol in is covered by their membership plan, nor that the plan identifier submitted with the request is one they actually hold, allowing any member to enrol themselves into restricted paid courses outside their plan and beyond the number of courses it entitles them to.
CVE-2026-95811 is an authorization bypass vulnerability in Lemonldap::NG::Handler for Perl. It affects versions from 2.0.0 before 2.16.10, from 2.17.0 before 2.21.6, and from 2.22.0 before 2.23.4. The vulnerability arises because the handler matches locationRules regular expressions against the raw request URI, while the web server routes on a normalized and percent-decoded path. This mismatch allows an attacker to bypass locationRules restrictions by using equivalent path spellings with percent-encoding, dot segments, or double slashes. Only virtual hosts whose default rule is more permissive than other rules are affected, allowing authenticated users to access URLs that should be restricted by locationRules but only with the permissions of the default rule.
The Botslab G980H dash camera firmware contains an authorization vulnerability in its session based command functionality. The product does not sufficiently associate an authenticated session with the client connection that established it, and subsequent privileged operations rely on possession of a valid session identifier without adequately validating the requesting client's authenticated context. An unauthenticated attacker with adjacent network access could potentially use valid session state associated with another client to access privileged functionality.
DBHub is a database MCP server for Postgres, MySQL, SQL Server, Oracle, MariaDB, SQLite. Prior to version 0.22.6, setting `readonly = true` on the `execute_sql` tool does not make the connection read-only. The connectors are written to set PostgreSQL `default_transaction_read_only=on` (and open SQLite in `readOnly` mode), but that code is gated on a config value that is never populated, so it never runs. The only thing left enforcing read-only is a classifier that inspects the first keyword of each statement. Any `SELECT` that writes or has side effects through a function call passes it. With an ordinary role this allows sequence tampering; with a privileged role it allows writing arbitrary files on the server (`lo_export`), reading arbitrary host files (`pg_read_file`), and remote code execution (`dblink` + `COPY ... TO PROGRAM`). The HTTP transport is unauthenticated and binds to `0.0.0.0` by default, so this is reachable by any network caller of `/mcp`. Version 0.22.6 patches the issue.
OpenWA versions prior to 0.23.5 contain an authorization flaw in the GET /api/sessions/{sessionId}/groups/{groupId}/invite-code endpoint and the GroupGetInviteCode MCP tool. These endpoints lack the required OPERATOR role check, allowing users with a VIEWER key scoped to a session to retrieve active group invite codes. Since invite codes allow joining WhatsApp groups, unauthorized users can join groups, gain read and post access, and maintain membership even after VIEWER key revocation. The issue is fixed in version 0.23.5.
authentik is an open-source identity provider. Prior to 2026.2.7, 2026.5.7, and 2026.8.2, an account with delegated permission to manage a group, group membership, or a user can grant superuser status to an account or assign an existing role to a group without holding the permissions that gate those privileges. Group hierarchy checks do not consistently account for superuser status inherited from ancestor groups, and role assignment to a group lacks the required authorization check. Only deployments that delegate these management capabilities to accounts that are not full administrators are affected. This issue is fixed in versions 2026.2.7, 2026.5.7, and 2026.8.2.
A missing authorization vulnerability exists in the Task Group APIs of Apache DolphinScheduler. The affected APIs do not properly verify whether the authenticated user has permission to access the project associated with the target Task Group.
This issue affects Apache DolphinScheduler: before 3.4.3.
Users are recommended to upgrade to version 3.4.3, which fixes the issue.
Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.20, the KleverUpdateAccountPermission built-in authorizes replacement of a target account's permissions by checking attacker-controlled vmInput.RecipientAddr instead of authenticated vmInput.CallerAddr. An attacker-controlled contract can choose a victim account with configured permissions as RecipientAddr, and contractHasValidPermission can accept the victim's default self-signer as authorization. UpdatePermission can then replace the victim's entire permission set with attacker-supplied Owner permissions, enabling asset theft or permanent lockout without a victim key or signature. Accounts without stored permissions and the native transaction path are not affected. This issue is fixed in version 1.7.20.
Moquette is a lightweight Java MQTT broker. Prior to 0.18.1, when pattern-based ACL rules are configured, AuthorizationsCollector.canDoOperation substitutes client ID and username values directly into rules containing %c or %u and then treats the result as an MQTT topic filter. A client that uses + or # in either identity can broaden the substituted filter and gain cross-tenant read and write access. A # identity can also produce an invalid filter that triggers a NullPointerException in Topic.match and disrupts session processing. This issue is fixed in version 0.18.1.
The Paid Membership Subscriptions WordPress plugin before 3.1.0 does not bind one of its unauthenticated payment actions to the requesting user, allowing someone who holds another member's in-flight payment identifier to delete that member's checkout state.
The Events Calendar WordPress plugin before 6.17.5 does not perform a per-object capability check on one family of its REST write routes, allowing users with a low-privilege role such as contributor to modify, unpublish, trash and take ownership of records belonging to other users, including administrators.