The AI Engine WordPress plugin before 3.6.4 does not verify ownership of a guest's uploaded chatbot files before deletion, authorising the action solely by a client-supplied session cookie value, so an unauthenticated attacker who obtains a victim's session identifier and file reference can delete that victim's uploaded files.
The Dokan: AI Powered WooCommerce Multivendor Marketplace Solution WordPress plugin before 5.0.11 does not verify that a downloadable product belongs to the requesting vendor before granting download permissions through one of its order REST endpoints, allowing an authenticated vendor to grant their own customer free download access to another vendor's paid downloadable files.
PraisonAI is a multi-agent teams system. Versions prior to 0.1.4 of the PraisonAI Platform API have two authorization failures that together break workspace isolation. The service layer for issues and projects performs global primary-key lookups without checking workspace ownership, so any authenticated user can read, modify, and delete resources in any workspace just by swapping UUIDs in their API requests. On top of that, every member management endpoint (add, update role, remove) only requires `min_role="member"`, which lets any workspace member promote themselves to owner and kick out the original owner. A low-privilege member of one workspace can steal data from every other workspace and take over any workspace they belong to. Both issues come from the same gap: the route layer pulls `workspace_id` from the URL and verifies membership, but the service layer ignores the workspace scope for resource lookups and ignores the caller's role level for member operations. The `require_workspace_member()` dependency does its job correctly. The problem is that the service layer doesn't use the information it provides. Version 0.1.4 of the PraisonAI Platform API patch the issue.
The MStore API WordPress plugin before version 4.21.0 contains an authorization bypass vulnerability in its vendor-orders endpoint. This flaw allows any authenticated user, including those with minimal privileges such as Subscribers, to access all WooCommerce orders and associated customer personal information. The vulnerability arises because the endpoint does not restrict access to only the caller's own orders.
A vulnerability in the Subscriptions for WooCommerce WordPress plugin before version 2.0.1 allows any authenticated customer to view another customer's subscription details by supplying the subscription ID. The plugin does not verify ownership of the subscription before displaying its information.
Flowise through 3.1.4 contains an insecure direct object reference vulnerability in the OpenAI Assistants integration that allows authenticated attackers to access credentials belonging to other workspaces by supplying an arbitrary credential UUID to Assistants endpoints without workspace ownership verification. Attackers can enumerate cross-workspace assistant metadata, retrieve file and vector store listings, and upload files into victim workspaces by exploiting the missing workspace-scoped authorization check in the credential lookup logic.
Statamic CMS versions prior to 5.74.1 and 6.24.0 contain an authorization bypass vulnerability allowing authenticated Control Panel users to view content from entries they do not have permission to access, including unpublished entries. The vulnerability does not allow modification of data. This issue is fixed in versions 5.74.1 and 6.24.0.
diboot-core's POST /common/load-related-data endpoint resolves caller-supplied field names to any @TableField column of any entity and returns those values for all rows, with no field or entity allowlist. The only guard, relatedDataSecurityCheck(), returns true unconditionally, so any authenticated user (including a zero-role account) can read @JsonIgnore-annotated secret fields such as IamAccount.authSecret and IamAccount.secretSalt for every account, or arbitrary secret fields of any other entity. Shiro's two-iteration MD5 with an 8-character salt is trivially crackable offline, so the disclosed admin password hashes convert to full administrative takeover. The endpoint is not example code; the official diboot-admin-ui frontend requires it, so deployments following the vendor's recommended integration expose it. The mechanism was renamed relatedData* to attachMore* on the development branch, but attachMoreSecurityCheck() also returns true unconditionally.
A vulnerability was identified in SourceCodester Online Examination & Learning Management System 1.0. Impacted is an unknown function of the file view_students.php. Such manipulation of the argument class_group leads to authorization bypass. The attack may be launched remotely.
CVE-2026-19111 is an authorization bypass vulnerability in Amazon Strands Agents Tools versions before 0.8.3. It affects the mongodb_memory, elasticsearch_memory, and mem0_memory tools, allowing remote authenticated users to access, modify, or delete memories of other tenants by manipulating the namespace parameter in tool calls. This issue is addressed by upgrading to version 0.8.3.
A vulnerability was found in SourceCodester Online Examination & Learning Management System 1.0. This vulnerability affects unknown code of the file /view.php. The manipulation of the argument ID results in authorization bypass. The attack can be launched remotely.
The Five Star Restaurant Reservations WordPress plugin before version 2.7.23 has a vulnerability where it does not verify the authenticity of incoming payment notifications. This flaw allows unauthenticated attackers to mark arbitrary pending reservations as paid and confirmed without validating the payment recipient, amount, status, or binding the notification to the intended booking.
The Events Made Easy WordPress plugin before version 3.1.2 contains an authorization bypass vulnerability. This flaw allows unauthenticated attackers to manipulate payment authorization tokens, enabling them to pay a lower amount for a cheap booking while marking a separate, higher-priced booking as fully paid. The vulnerability is classified as CWE-639, indicating improper authorization through user-controlled keys. The issue has a medium severity with a CVSS score of 5.3.
Payment Plugins for PayPal WooCommerce versions before 2.0.20 contain a missing authorization vulnerability in a REST endpoint. This flaw allows unauthenticated users to bypass payment authorization checks, potentially enabling unauthorized payment actions. The vulnerability is identified as CWE-862 (Missing Authorization) and CWE-639. It has a high severity score of 7.5 (CVSS 3.1) with no confidentiality or availability impact but a high integrity impact. No official patch or remediation guidance is currently confirmed.
Tutor LMS WordPress plugin versions before 3.9.14 have an authorization bypass vulnerability. Authenticated users with subscriber-level access or higher who are enrolled in at least one course can access paid lesson, quiz, and assignment content from other courses they are not enrolled in. This occurs due to improper verification of enrollment when restricting access to protected course content.
The Integrate PhonePe with WooCommerce WordPress plugin up to version 1.2.1 contains an authorization bypass vulnerability. It fails to verify that a payment transaction belongs to the order being marked as paid and does not authenticate payment-completion requests. This allows unauthenticated attackers to reuse a valid transaction to mark arbitrary orders as paid, bypassing payment requirements.
CVE-2026-18258 is an authorization bypass vulnerability in Scripta/eScriptorium version 26.04.1 and earlier. It affects several API endpoints, allowing a remote authenticated user to read, modify, and delete transcription content belonging to other users by manipulating primary keys in the request body. This occurs because the application queries a global model manager instead of a request-scoped queryset, bypassing proper authorization checks.
CVE-2026-18275 is an authorization bypass vulnerability in Scripta eScriptorium up to version 26.04.1. It allows a remote authenticated user to overwrite other users' document parts by exploiting improper queryset restrictions in the serializers handling process and annotation taxonomy. This issue arises because the queryset restriction was applied to the ManyRelatedField instead of its child_relation, rendering the restriction ineffective.