| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| Booking Agent Broken Access Control in QuickCal - Appointment Booking Calendar for WordPress <= 1.0.16 versions. |
| Unauthenticated Broken Access Control in MarketKing <= 2.1.40 versions. |
| Unauthenticated Broken Access Control in YT Player <= 2.0.9 versions. |
| Unauthenticated Broken Access Control in Autopay dla WooCommerce <= 2.2.27 versions. |
| Unauthenticated Broken Access Control in PayU India <= 3.8.9 versions. |
| Unauthenticated Broken Access Control in ShopLentor Pro <= 2.8.5 versions. |
| Subscriber Broken Access Control in ShopLentor Pro <= 2.8.5 versions. |
| Subscriber Broken Access Control in ЮKassa для WooCommerce <= 2.16.1 versions. |
| Unauthenticated Broken Access Control in Kit (formerly ConvertKit) <= 3.3.5 versions. |
| Subscriber Broken Access Control in Reviewer <= 3.14.2 versions. |
| Unauthenticated Broken Access Control in Content Control <= 2.6.5 versions. |
| Unauthenticated Broken Access Control in Event post <= 6.0.1 versions. |
| Unauthenticated Broken Access Control in Manual - Documentation, Knowledge Base & Education WordPress Theme <= 7.5.4 versions. |
| Contributor Broken Access Control in Avada Custom Branding <= 1.2 versions. |
| Unauthenticated Broken Access Control in Civi Framework <= 2.2.0 versions. |
| Subscriber Broken Access Control in Cyr to Lat reloaded – transliteration of links and file names <= 1.3.3 versions. |
| Dendrite through 0.13.8 contains an improper access control vulnerability in the syncapi /context endpoint (syncapi/routing/context.go) that allows authenticated local users to access post-leave room state events by exploiting a flawed membership check that evaluates only the RoomExists field while ignoring IsInRoom, HasBeenInRoom, and Membership fields. Attackers who have left a room can call the rooms context API endpoint for a previously permitted event and receive unfiltered current room state that the /messages and /sync endpoints correctly withhold. |
| n8n before 2.29.8 and 2.30.x before 2.30.1 (affected from 2.27.0, when the OAuth 2.1 consent and token-issuance flow was introduced) does not verify that the authenticated user has access to the workflow referenced as the OAuth resource. On instances with at least one active MCP Server Trigger workflow configured with n8n OAuth2 authentication, a member-level user can register an OAuth client, self-approve consent for another user's workflow, and obtain a valid token. The workflow then runs in the owner's project context with the owner's stored credentials, and the attacker can set tool inputs and read outputs (potentially including data from the owner's connected integrations), breaking user and project isolation. |
| A vulnerability was discovered in MongoDB Server where the server-side MozJS scripting engine unconditionally registered a module loading hook that enables JavaScript calls to read arbitrary files from the host filesystem using the mongod process's privileges. An authenticated user could exploit this through crafted aggregation pipeline commands to read sensitive files accessible to the MongoDB server process. |
| An authenticated user holding cursor termination privileges on one database may incorrectly be permitted to terminate active cursors on a separate database, disrupting ongoing query operations for other users. The behavior stems from an authorization check that does not correctly scope privileges to the appropriate namespace. |
