| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| Insertion of Sensitive Information Into Sent Data vulnerability in WPTasty Tasty Recipes Lite tasty-recipes-lite allows Retrieve Embedded Sensitive Data.This issue affects Tasty Recipes Lite: from n/a through 1.2.11. |
| In `github.com/eclipse-keypont/crypto11/v2` versions `<= 2.0.0-rc8` (and the deprecated v1 module paths `github.com/eclipse-keypont/crypto11 <= 1.6.8`, `github.com/ThalesGroup/crypto11 <= 1.7.0-rc1` and `github.com/ThalesIgnite/crypto11 <= 1.2.5`), the key-pair and certificate lookup functions (`FindKeyPair`, `FindKeyPairs`, `FindKeyPairsWithAttributes`, `FindAllKeyPairs`, the `FindRSAKeyPair*` family and `FindAllPairedCertificates`) pair a private key with a public key object, or with a certificate, by `CKA_ID`/`CKA_LABEL` alone, take the first match the token returns, and never verify that it belongs to the private key. PKCS#11 permits a session that has not logged in to create public token objects, so anyone able to open a session on the token — without the PIN — can plant a public key or certificate carrying a victim key's `CKA_ID` and label, and crypto11 may return it as that key's public half. An application that publishes or trusts `Signer.Public()` (a JWKS endpoint, a key registry, `authorized_keys`, a CSR) then publishes the attacker's key, and relying parties accept anything the attacker signs as coming from the service. On the v1 line the lookup also falls back to a class-and-key-type-only search when the private key has no `CKA_ID`, pairing a label-only private key with the first public key of its type on the token.
The v1 module paths are deprecated and will not be fixed; users should migrate to github.com/eclipse-keypont/crypto11/v2 version 2.0.0-rc9 or later. |
| Authentication Bypass Using an Alternate Path or Channel vulnerability in miniOrange miniorange otp verification miniorange-otp-verification allows Authentication Abuse.This issue affects miniorange otp verification: from n/a through 5.6.1. |
| In JetBrains TeamCity before 2026.2.1, 2026.1.5 the TFS helper server was exposed on all network interfaces |
| In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via boot classpath libraries in the Kotlin DSL sandbox |
| In JetBrains TeamCity before 2026.2.1, 2026.1.5 privilege escalation was possible via username handling in token authentication |
| In JetBrains TeamCity before 2026.2.1 stored XSS on the change Files tab was possible |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via local repository URLs in Subversion VCS roots |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via Maven repository settings |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via Git VCS root URLs |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS in Server Health reports was possible |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 vCS root credentials could be exposed via change viewer links |
| In JetBrains IntelliJ IDEA before 2026.3, 2026.2.4 code execution was possible in untrusted projects via the Code Provenance plugin |
| In JetBrains YouTrack before 2026.2.19840 improper authorization allowed read-only users to change issue fields via agile boards |
| In JetBrains YouTrack before 2026.2.19840 an HTML injection in email notifications was possible via issue descriptions |
| In JetBrains YouTrack before 2026.2.19840 private issue summaries and descriptions could be read via agile board queries for archived projects |
| Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in InstaWP InstaWP Connect instawp-connect allows Blind SQL Injection.This issue affects InstaWP Connect: from n/a through 0.1.4.4. |
| The Photo Gallery, Sliders, Proofing and Themes – NextGEN Gallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 4.5.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires the plugin's "What must the lightbox be applied to?" setting (thumbEffectContext) to be configured as "Try to apply to all images" or "Try to apply to all images that link to image files," which is not the shipping default, and also requires the attacker's comment to reach a publicly rendered state. |
| The Pie Register – User Registration, Profiles & Content Restriction plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 3.8.4.17 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to overwrite the role of the site's primary administrator account (user ID 1) with the registration form's configured role, demoting the administrator to a lower-privileged role and locking them out of wp-admin. This vulnerability is exploitable only on PHP 8+, where casting a WP_Error object to int yields 1, causing the role modification to target user ID 1. |
| Confused deputy in DevTools in Google Chrome prior to 158.0.8127.36 allowed a remote attacker leveraging social engineering to bypass web origin policy via a crafted HTML page. (Chromium security severity: Low) |