Securly vulnerabilities
We track 6 vulnerabilities in Securly products across 2 products. 6 are rated high or critical, and none are known to be exploited. The most recent was published on June 3, 2026.
Latest Securly vulnerabilities
- 7.5 High severity
Securly Chrome Extension: Inefficient Algorithmic Complexity
Version 3.0.7 of the Securly Chrome Extension uses deprecated SHA-1 hashing for IWF CSAM URL matching (25,020 hashes) and CIPA blocklist matching (12,352 hashes).
- 7.5 High severity
Securly Chrome Extension: Improper Neutralization of Special Elements used in an Expression Language Statement
Version 3.0.7 of the Securly Chrome Extension downloads config.json over HTTP and compiles server-provided patterns as JavaScript regular expressions via new RegExp() without complexity validation. An on-path attacker can inject specific patterns to cause cata
- 7.5 High severity
Securly Chrome Extension: Inclusion of Functionality from Untrusted Control Sphere
Version 3.0.7 of the Securly Chrome Extension dynamically registers content13.min.js as a content script via chrome.scripting.registerContentScripts() at runtime. This script is NOT declared in manifest.json and bypasses Chrome Web Store static security review
- 7.5 High severity
Securly Chrome Extension: Inadequate Encryption Strength
Version 3.0.7 of the Securly Chrome Extension exposes multiple publicly accessible endpoints that allow unauthenticated access to sensitive data. The exposed information consists of SHA-1 hashes that are inadequately obfuscated using a simple Caesar cipher, wh
- 7.3 High severity
Securly Chrome Extension: Use of Hard-coded Credentials
Version 3.0.7 of the Securly Chrome Extension contains hardcoded, plaintext AES passphrases in securly.min.js. These keys decrypt crisis alert keyword data and intervention site data.
- 7.1 High severity
Securly Chrome Extension: Cleartext Transmission of Sensitive Information
Version 3.0.7 of the Securly Chrome Extension downloads JSON files containing crisis alert keywords and filtering rules over unencrypted HTTP via the Fetch API. Other endpoints in the same extension correctly fetch IWF and CIPA data over HTTPS, demonstrating a