Description
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 an inconsistent implementation of TLS.
Published: 2026-06-03
Score: 7.1 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability allows the Securly Chrome Extension to download JSON files containing crisis alert keywords and filtering rules over cleartext HTTP, exposing sensitive security information. Because the extension fetches this data via the Fetch API without encryption, an attacker able to intercept network traffic could read or modify these files. This leads to potential data exposure and manipulation of filtering behavior, undermining the integrity of the extension’s content filtering mechanisms.

Affected Systems

The affected product is the Securly Chrome Extension, version 3.0.7. The vendor Securly released an extension for Chrome that was found to use unencrypted HTTP for certain data requests in that version.

Risk and Exploitability

The CVSS score is 7.1 and the EPSS score is <1%, indicating that exploitation is unlikely but possible. The vulnerability is not listed in CISA KEV. The likely attack vector is eavesdropping on the user’s network traffic; by intercepting the cleartext HTTP request, an attacker could read or tamper with the JSON files. Because the data contains crisis alert keywords and filtering rules, the attacker gains information that could help craft attacks or change filtering behavior, but no remote code execution is possible. Overall, the risk is moderate to high for environments that rely on the Securly Chrome Extension for filtering content.

Generated by OpenCVE AI on June 4, 2026 at 16:52 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update the Securly Chrome Extension to a version that retrieves data over HTTPS
  • Disable or block the use of the Securly Chrome Extension until a secure version is available
  • Configure network and browser policies to prevent HTTP requests from Chrome extensions

Generated by OpenCVE AI on June 4, 2026 at 16:52 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

References
History

Fri, 05 Jun 2026 21:00:00 +0000

Type Values Removed Values Added
First Time appeared Securly securly
CPEs cpe:2.3:a:securly:securly:3.0.7:*:*:*:*:chrome:*:*
Vendors & Products Securly securly

Fri, 05 Jun 2026 10:45:00 +0000

Type Values Removed Values Added
First Time appeared Securly
Securly chrome Extension
Vendors & Products Securly
Securly chrome Extension

Thu, 04 Jun 2026 15:15:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 03 Jun 2026 20:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-319

Wed, 03 Jun 2026 19:00:00 +0000

Type Values Removed Values Added
Description 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 an inconsistent implementation of TLS.
Title CVE-2026-8874
References

Subscriptions

Securly Chrome Extension Securly
cve-icon MITRE

Status: PUBLISHED

Assigner: certcc

Published:

Updated: 2026-06-04T14:43:00.488Z

Reserved: 2026-05-18T20:26:19.787Z

Link: CVE-2026-8874

cve-icon Vulnrichment

Updated: 2026-06-04T14:39:43.480Z

cve-icon NVD

Status : Analyzed

Published: 2026-06-03T19:16:39.090

Modified: 2026-06-05T20:47:12.477

Link: CVE-2026-8874

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-06-05T10:11:29Z

Weaknesses
  • CWE-319

    Cleartext Transmission of Sensitive Information