Export limit exceeded: 13661 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (13661 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-81035 | 1 Midday-ai | 1 Midday | 2026-08-28 | 8.1 High |
| Midday allows any member of a team to delete it. The delete procedure in apps/api/src/trpc/routers/team.ts authorises the caller with the team-access helper, which returns true for every row in the team-membership table irrespective of the role it records, and the data-layer function it calls re-checks the same helper and nothing else. The neighbouring procedures that remove or update a member in the same router each resolve the caller's role and refuse the request unless it is owner, so the check exists in the file and is not applied to deletion. Member is the role an invited user receives, so any invitee can remove the team and every record scoped to it, and the deletion enqueues the cleanup job with the stored bank-connection tokens, which the job then uses against the connected providers. The update procedure in the same router carries no role check either. | ||||
| CVE-2026-81284 | 2 Acf Extended, Wordpress | 2 Acf Extended, Wordpress | 2026-08-28 | 4.3 Medium |
| Contributor Broken Access Control in ACF Extended <= 0.9.2.6 versions. | ||||
| CVE-2026-81767 | 2 Wordpress, Yalla Ya! | 2 Wordpress, Simple Payment | 2026-08-28 | 7.5 High |
| Unauthenticated Broken Access Control in Simple Payment <= 2.5.2 versions. | ||||
| CVE-2026-68929 | 1 Labring | 1 Fastgpt | 2026-08-28 | N/A |
| FastGPT is an open-source LLM platform for building AI applications on a knowledge base. In versions prior to 4.15.2, the WeChat (iLink) share-channel endpoints authorize requests using only the public shareId, with no authenticated identity or team-ownership check. As a result, an unauthenticated attacker who knows a victim team's shareId can take that team's WeChat bot offline or hijack the channel to their own bot: the logout endpoint is gated only by an existence check yet wipes the outLink's stored WeChat token, and the QR-code status endpoint performs no authorization at all and writes attacker-supplied bot credentials into the outLink identified by shareId. By generating a QR for a victim shareId, scanning it with their own WeChat, and calling the status endpoint, an attacker binds the victim team's app to the attacker's bot, exposing the app's private responses, displacing the legitimate binding, and consuming the victim's resources. The shareId is exposed in every shared chat URL, iframe, and embed, so it is not a secret. This issue is fixed in version 4.15.2. | ||||
| CVE-2026-18886 | 1 Servicenow | 1 Servicenow Ai Platform | 2026-08-28 | N/A |
| ServiceNow has remediated an improper access control vulnerability that was identified in the ServiceNow AI platform. This vulnerability could enable an unauthenticated user, in certain circumstances, to create or modify instance data beyond what was intended, resulting in privilege escalation. ServiceNow deployed a security update to hosted instances and ServiceNow provided the update to our partners and self-hosted customers. We are not currently aware of exploitation against ServiceNow instances. We recommend customers promptly apply appropriate updates or upgrade to a patched release if they have not already done so. | ||||
| CVE-2026-79174 | 1 Google | 1 Chrome | 2026-08-28 | 4.3 Medium |
| Incorrect authorization in Extensions in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to bypass web origin policy into a privileged page via a crafted HTML page. (Chromium security severity: High) | ||||
| CVE-2026-79222 | 1 Google | 2 Android, Chrome | 2026-08-28 | 4.3 Medium |
| Incorrect authorization in CustomTabs in Google Chrome on on Android prior to 152.0.7977.65 allowed a local attacker to bypass web origin policy via a co-installed app. (Chromium security severity: Medium) | ||||
| CVE-2026-79238 | 1 Google | 1 Chrome | 2026-08-28 | 4.3 Medium |
| Incorrect authorization in ServiceWorker in Google Chrome prior to 152.0.7977.65 allowed a remote attacker leveraging social engineering to bypass web origin policy via a crafted Chrome extension. (Chromium security severity: Medium) | ||||
| CVE-2026-78954 | 1 Google | 1 Chrome | 2026-08-28 | 4.3 Medium |
| Incorrect authorization in Extensions in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to bypass web origin policy via a crafted HTML page. (Chromium security severity: High) | ||||
| CVE-2026-79237 | 1 Google | 1 Chrome | 2026-08-28 | 4.3 Medium |
| Incorrect authorization in Navigation in Google Chrome prior to 152.0.7977.65 allowed a remote attacker to bypass web origin policy via a crafted HTML page. (Chromium security severity: Medium) | ||||
| CVE-2026-79212 | 1 Google | 1 Chrome | 2026-08-28 | 4.3 Medium |
| Missing authorization in Passwords in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process and leveraged social engineering to bypass web origin policy via a crafted HTML page. (Chromium security severity: High) | ||||
| CVE-2026-79093 | 1 Google | 1 Chrome | 2026-08-28 | 4.3 Medium |
| Incorrect authorization in Paint in Google Chrome prior to 152.0.7977.65 allowed a remote attacker to potentially bypass web origin policy via a crafted HTML page. (Chromium security severity: High) | ||||
| CVE-2026-79228 | 1 Google | 1 Chrome | 2026-08-28 | 3.1 Low |
| Incorrect authorization in SiteIsolation in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to bypass site isolation into a privileged page via a crafted HTML page. (Chromium security severity: Medium) | ||||
| CVE-2026-79002 | 1 Google | 1 Chrome | 2026-08-28 | 3.1 Low |
| Incorrect authorization in SiteIsolation in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page. (Chromium security severity: Medium) | ||||
| CVE-2026-79205 | 1 Google | 1 Chrome | 2026-08-28 | 4.3 Medium |
| Incorrect authorization in Network in Google Chrome prior to 152.0.7977.65 allowed a remote attacker to bypass web origin policy via a crafted HTML page. (Chromium security severity: Medium) | ||||
| CVE-2026-79085 | 1 Google | 1 Chrome | 2026-08-28 | 4.3 Medium |
| Missing authorization in Network in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to bypass web origin policy via a crafted HTML page. (Chromium security severity: Medium) | ||||
| CVE-2026-78961 | 1 Google | 1 Chrome | 2026-08-28 | 4.3 Medium |
| Incorrect authorization in Core in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process and leveraged social engineering to bypass web origin policy via a crafted HTML page. (Chromium security severity: Medium) | ||||
| CVE-2026-79248 | 1 Google | 1 Chrome | 2026-08-28 | 4.3 Medium |
| Incorrect authorization in Input in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to bypass web origin policy via a crafted HTML page. (Chromium security severity: Medium) | ||||
| CVE-2026-79184 | 1 Google | 1 Chrome | 2026-08-28 | 4.3 Medium |
| Missing authorization in Preload in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to bypass web origin policy via a crafted HTML page. (Chromium security severity: Low) | ||||
| CVE-2026-79190 | 1 Google | 1 Chrome | 2026-08-28 | 4.3 Medium |
| Incorrect authorization in Extensions in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to bypass web origin policy via a crafted HTML page. (Chromium security severity: Low) | ||||