Threats
CVEs published in the last 120 days, plus everything on CISA’s known-exploited list. Scores, exploit likelihood and exploitation status in one place.
| Score | CVE | Affected | EPSS | Published |
|---|---|---|---|---|
| — unscored | CVE-2026-94299 | elegro Crypto Payment The elegro Crypto Payment WordPress plugin through 1.0.1 does not require a shared secret to be configured before trusting incoming payment notification requests, allowing unauthenticated attackers to forge payment confirmations and change the status of arbitrary orders on any installation where that secret has been left at its default empty value. | — | 6 Oct 2026 |
| 9.3 critical | CVE-2026-94293 | Murrelektronik Software AAS Edge Client all versions An unauthenticated remote attacker can modify Asset Administration Shell submodel data via PATCH requests and can read all data exposed by the GET endpoints. | — | 6 Oct 2026 |
| — unscored | CVE-2026-94278 | File Media Renamer The File Media Renamer WordPress plugin through 1.3 does not verify that the requesting user is authorised to modify a given media attachment, allowing any user with file-upload privileges to rename attachments belonging to other users, including administrators, and to corrupt unrelated stored site data that referenced the old file path. | — | 6 Oct 2026 |
| — unscored | CVE-2026-94271 | Deema Payment Gateway The Deema Payment Gateway WordPress plugin through 1.1.2 does not verify the payment with the payment provider when handling the return from the hosted checkout, and does not check the payment status or amount, allowing unauthenticated users to have orders marked as paid without any payment being taken. | — | 6 Oct 2026 |
| — unscored | CVE-2026-94270 | Deema Payment Gateway The Deema Payment Gateway WordPress plugin through 1.1.2 does not verify the authenticity of incoming payment provider notifications, and ships with that verification disabled by default, allowing unauthenticated attackers to mark an unpaid order as paid, or to cancel or refund an existing order. | — | 6 Oct 2026 |
| — unscored | CVE-2026-89289 | Fast Courier The Fast Courier WordPress plugin through 5.2.3 does not restrict an unauthenticated REST route that writes order fulfillment data, allowing unauthenticated attackers to overwrite the courier status and customer-facing tracking details of any WooCommerce order by supplying its id. | — | 6 Oct 2026 |
| — unscored | CVE-2026-86786 | Slider Pro The Slider Pro WordPress plugin through 1.0.0 does not perform any capability or authorisation check on one of its AJAX actions, allowing unauthenticated users to retrieve the title, excerpt and permalink of non-public posts, including drafts, pending, scheduled, private and trashed posts, as well as post revisions and media metadata. | — | 6 Oct 2026 |
| 7.6 high | CVE-2026-59358 | Cloud Foundry UAA Improper authentication (CWE-287) in the OAuth token endpoint in Cloud Foundry UAA allows a remote, authenticated attacker holding a valid user access token to obtain a fully-privileged client_credentials token for the OAuth client that issued it, by presenting the user token as an OAuth 2.0 Bearer credential on a client_credentials grant request in place of the client’s configured secret. UAA’s client_credentials handling does not verify that the Bearer credential supplied for client authentication is actually a client credential (a client secret or a valid configured client authentication method); it accepts any valid access token whose client_id matches the request. A token obtained by a normal end user through a public authorization_code + PKCE flow — scoped only to uaa.user, carrying a user_id, and recording client_auth_method=none — satisfies this check. That user token cannot itself administer OAuth clients (POST /oauth/clients correctly returns 403), but when replayed as Bearer authentication on a client_credentials request for the same client, UAA issues a new client-only token carrying the client’s full authorities, such as clients.write. An attacker can use that token to create arbitrary new OAuth clients, including clients with attacker-chosen authorities, without ever possessing the client’s actual secret. Exploitation requires a valid user access token (the attacker’s own) for a client that is configured to support both a public, user-facing authorization flow and the client_credentials grant type on the same client_id — a non-default combination. Practical impact scales with the authorities assigned to that client. | — | 6 Oct 2026 |
| 6.5 medium | CVE-2026-59357 | Cloud Foundry UAA Insufficient verification of data authenticity (CWE-345) in the external OIDC login callback in Cloud Foundry UAA v4.5.0 to v79.6.0 (inclusive) allows an authenticated UAA user to bypass the OAuth authorization-code exchange and establish an authenticated external-OIDC browser session, via submitting a UAA access token or a cross-client ID token as the callback’s id_token parameter. The issue only manifests when a UAA zone is configured with an OIDC identity provider whose issuer exactly matches that zone’s own /oauth/token endpoint (a “self-UAA” OIDC configuration). In this configuration, the callback takes a supplied id_token directly instead of requiring the authorization code exchange, and does not verify that the token was actually issued as an ID token for the specific self-OIDC relying-party client. An attacker holding any valid UAA JWT for themselves — including a plain access token with only uaa.user scope, or a valid ID token issued to an unrelated client such as cf — can present it as the callback’s id_token and be authenticated into a mapped local (“shadow”) account. Because the resulting session is not verified against the originating token’s true audience or user_id, its effective privilege depends entirely on the shadow account’s group memberships, which can include administrative scopes such as clients.write. Exploitation requires a valid UAA user JWT, a valid browser login state for the target zone, and the presence of a self-referential OIDC provider configuration — this is not a pre-authentication vulnerability, and does not by itself grant privileges beyond those already held by the mapped shadow account. | — | 6 Oct 2026 |
| 7.8 high | CVE-2026-57559 | Qualcomm, Inc. Snapdragon Memory corruption while processing service requests. | — | 6 Oct 2026 |
| 7.8 high | CVE-2026-57555 | Qualcomm, Inc. Snapdragon Memory Corruption when executing system service routines due to improper handling of user input buffers. | — | 6 Oct 2026 |
| 7.8 high | CVE-2026-57554 | Qualcomm, Inc. Snapdragon Memory Corruption when asynchronous threads access shared performance counter data simultaneously during FastRPC invocations. | — | 6 Oct 2026 |
| 7.5 high | CVE-2026-57546 | Qualcomm, Inc. Snapdragon Transient DOS when processing a continuous receive command with a zero-sized global configuration override. | — | 6 Oct 2026 |
| 7.8 high | CVE-2026-57545 | Qualcomm, Inc. Snapdragon Memory corruption when processing draw objects of incorrect type during graphics command list execution. | — | 6 Oct 2026 |
| 7.8 high | CVE-2026-57537 | Qualcomm, Inc. Snapdragon Memory Corruption when accessing and modifying geographic mapping data concurrently without proper synchronization. | — | 6 Oct 2026 |
| 7.1 high | CVE-2026-25302 | Qualcomm, Inc. Snapdragon Cryptographic Issue when processing non-ELF partitions, authentication and signature checks are bypassed, allowing unsigned or corrupted images to be mounted and processed. | — | 6 Oct 2026 |
| 7.8 high | CVE-2026-25291 | Qualcomm, Inc. Snapdragon Memory corruption when performing concurrent operations on shared memory page lists due to lack of proper synchronization mechanisms. | — | 6 Oct 2026 |
| 6.7 medium | CVE-2026-25274 | Qualcomm, Inc. Snapdragon Memory Corruption when processing concurrent DMA buffer allocation and deallocation commands without proper synchronization. | — | 6 Oct 2026 |
| 6.7 medium | CVE-2026-25273 | Qualcomm, Inc. Snapdragon Memory Corruption when processing camera operations due to out-of-bounds write during driver updates. | — | 6 Oct 2026 |
| 6.7 medium | CVE-2026-25272 | Qualcomm, Inc. Snapdragon Memory Corruption when processing camera CRE driver operations with improper handling of buffer limits during hardware update preparation. | — | 6 Oct 2026 |