| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| In JetBrains TeamCity before 2026.2, 2026.1.4 improper authorization allowed project agent administrators to manage agents of other projects |
| In JetBrains TeamCity before 2026.2 project administrators could read OAuth connection secrets of ancestor projects |
| In JetBrains TeamCity before 2026.2 mute and unmute operations via XML-RPC could be attributed to other users |
| In JetBrains TeamCity before 2026.2.1 improper authorization allowed using AWS connections of other projects in cloud profiles |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 improper authorization allowed queuing builds with personal changes of other users |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 improper authorization allowed overwriting versioned settings of other projects |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 improper authorization allowed publishing packages to NuGet feeds of other projects |
| Joomla Extension - vi-solutions - IDOR in backend data export in Visforms extension 1.0.0-5.6.4, 6.0.0-6.2.1 - The backend export did not correctly verify permissions for the exported form, allowing backend users to export data of forms they are not authorized to access. |
| The checkout of JTL-Shop stores the delivery address
ID submitted by the customer in the session and adopts it into the order
without verifying that the address belongs to the ordering customer. A remote
attacker with access to the checkout, including a guest, can thereby attach
the delivery address of another customer to their own order. Name and
address of the other customer, and depending on the shop configuration
further contact data, then appear in the order confirmation and customer
account. As the IDs are sequential, addresses can be enumerated. Goods may
also be shipped to the wrong address. |
| Authorization bypass through a user-controlled key in the PuppetDB facts terminus used by Puppet Server allows a client holding any valid agent certificate to overwrite the facts, including trusted facts, that PuppetDB stores for a different node. In Puppet Enterprise deployments where task permissions are scoped to node groups defined by facts or trusted facts, this can allow a user to run tasks on nodes outside their permitted scope. |
| Dell PowerStore contains an authorization bypass vulnerability. A remote attacker could exploit this vulnerability to act under another user's session, potentially leading to denial of service. |
| Rocket.Chat versions 0.61.0 before 3.11.4, 3.12.x before 3.12.4 and 3.13.x before 3.13.2 contain a missing authorization vulnerability allowing unauthenticated attackers to read any room's messages via the livechat:loadHistory Meteor method. Attackers can mint a guest token through livechat:registerGuest and send POST requests to /api/v1/method.callAnon with a target rid parameter to retrieve message history without membership checks. Exploitation evidence was first observed by the Shadowserver Foundation on 2025-02-13. |
| In JetBrains TeamCity before 2026.1.3, 2025.11.7 DoS via agent command results was possible |
| LibreChat is an enhanced ChatGPT clone that supports multiple AI providers. Prior to 0.8.6, POST /api/messages/:conversationId authorizes req.params.conversationId in api/server/middleware/validateMessageReq.js but persists attacker-controlled req.body.conversationId through api/server/routes/messages.js. An authenticated attacker can use an owned conversation in the URL while naming a victim conversation in the body, causing an attacker-controlled message to be stored in the victim conversation. This issue is fixed in version 0.8.6. |
| LibreChat is an enhanced ChatGPT clone that supports multiple AI providers. Prior to 0.8.7, packages/data-schemas/src/methods/file.ts updateFileUsage accepts chat attachment files[].file_id values without restricting the lookup to the authenticated owner. An authenticated attacker who obtains another user's file identifier, including through GET /api/share/{shareId} for a shared conversation, can attach that file to a chat, causing extracted document text to enter the model context. The same operation can remove expiration metadata from the victim file. This issue is fixed in version 0.8.7. |
| Authenticated users can bypass normal controls on the reading and writing of workflow execution results. This allows any authenticated user to read or modify any other user's workflow execution results.
This issue affects Apache Texera (incubating): from 1.1.0-incubating before 1.3.0-incubating.
Users are recommended to upgrade to version 1.3.0-incubating, which fixes the issue. |
| LinkAce is a self-hosted archive to collect website links. Prior to 2.5.9, the authenticated GET /api/v2/lists/{list}/links endpoint in app/Http/Controllers/API/ListLinksController.php authorizes access only to the parent list and then returns its links without applying visibleForUser(). Because another user's INTERNAL or PUBLIC list may legitimately contain PRIVATE links, a normal authenticated user who may view the list can also receive those private link records, including their URLs, titles, descriptions, icons, and timestamps. Equivalent web, tag, notes, and feed handlers apply the per-link visibility scope, so this API handler is the affected exception. This issue is fixed in version 2.5.9. |
| LinkAce is a self-hosted archive to collect website links. Prior to 2.6.0, LinkController::update() in app/Http/Controllers/API/LinkController.php passes $request->all() to the repository update method even though user_id is fillable and is not an allowed field in the validated update request. An authenticated API user who is authorized to update a link can therefore assign an arbitrary or nonexistent user_id, transferring the link into another user's bookmark collection or orphaning it from any real account. The web update controller is unaffected because it passes only validated fields. This issue is fixed in version 2.6.0. |
| LinkAce is a self-hosted archive to collect website links. Prior to 2.6.0, the authenticated GET /lists/{list}/feed and GET /tags/{tag}/feed handlers in app/Http/Controllers/App/FeedController.php use integer route model binding without an object-level authorization or visibility check. Unlike the web list controller, which invokes LinkListPolicy::view(), the feed controller lets a normal authenticated user enumerate another user's private list or tag and receive its name and feed metadata, along with public or internal bookmark entries associated with that taxonomy. The existing per-link visibility filter still excludes PRIVATE link records, so the disclosure is limited to the private taxonomy and its non-private member links. This issue is fixed in version 2.6.0. |
| LinkAce is a self-hosted archive to collect website links. Prior to 2.6.0, the HTML bookmark import action in app/Actions/ImportHtmlBookmarks.php uses the global Link::whereUrl() lookup instead of restricting duplicate detection to the importing user. An authenticated user can submit a chosen URL and distinguish the skipped response count from the queued count to learn whether any account has saved that URL, including as a PRIVATE bookmark. The oracle reveals URL existence but does not directly return the bookmark contents or owner. This issue is fixed in version 2.6.0. |