Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim with extension to malicious page
-
DeliverySend crafted onMessageExternal message
-
ExploitBypass missing origin authorization
-
ExecutionExtension scrapes attacker-chosen URLs
-
ImpactExfiltrate scraped content to attacker page
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the victim to have the ByteDance Coze Scraper Chrome extension version <=2.0.2 installed AND to visit or interact with an attacker-controlled web page (UI:P/user interaction). The specific trigger is the extension's externally-exposed message listener chrome.runtime.onMessageExternal.addListener, which processes attacker-supplied body.url/body.urls, paginationConfig, xPathConfig and xPaths without verifying the sender's origin. Limiting factors: it only affects users of this niche extension, needs user interaction (loading the malicious page), and impact is confined to attacker-directed URL scraping with low confidentiality impact and no integrity/availability effect - there is no code execution or authenticated-account compromise. |
| Impact | This is a low-severity, missing-authorization flaw (CWE-862) in the ByteDance Coze Scraper Chrome extension (<=2.0.2), and the signals are consistent with genuinely low real-world risk despite a public exploit. The vendor-supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:P/VC:L, score 2.1) indicates a network-reachable but user-interaction-dependent issue with only low confidentiality impact and no integrity or availability impact - matching the description, where the extension's external message handler (chrome.runtime.onMessageExternal.addListener) accepts scraping parameters (body.url/urls, paginationConfig, xPathConfig, xPaths) from any website without authorization. E:P confirms proof-of-concept exploit code is public (GitHub write-up by xryj920 plus VulDB submission 904123 / vuln 409003). There is no EPSS score and no CISA KEV listing in the input, so there is no evidence of active or automated exploitation - this is publicly-documented but not weaponized at scale. The practical ceiling on impact is that exploitation requires a victim to have this specific niche extension installed and to visit an attacker-controlled page; the payoff is coercing the extension into scraping attacker-chosen URLs (potentially abusing the victim's browser context/IP), not code execution or broad data theft. Net: a real but minor issue, appropriately rated low; not a patching priority for most environments. |
| Exploit ScenarioDerived | An attacker hosts a malicious web page and, when a visitor who has the Coze Scraper extension (<=2.0.2) installed loads it, the page sends a chrome.runtime.onMessageExternal message supplying body.url/urls, xPathConfig and paginationConfig. Because the external message handler performs no origin authorization, the extension scrapes the attacker-specified URLs from within the victim's browser and returns the extracted content to the attacker's page. Public proof-of-concept code exists (GitHub xryj920 write-up and VulDB entry), lowering the effort to reproduce. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 23, 2026
Missing authorization in the ByteDance Coze Scraper Chrome extension (versions up to and including 2.0.2) allows any website to drive the extension's externally exposed message handler and make it scrape attacker-chosen URLs and extract page data along attacker-supplied XPath/pagination parameters. The flaw is in the chrome.runtime.onMessageExternal listener defined in static/background/index.js, which processes incoming messages without verifying the sender's origin; exploitation requires the victim to have this niche extension installed and to visit or interact with an attacker-controlled page, so real-world exposure is limited to that user base. A publicly available exploit write-up exists and the vendor was contacted but did not respond; CISA KEV does not list this issue, and the low EPSS/CVSS 4.0 score of 2.1 reflects limited confidentiality impact with no integrity or availability effect and no code execution.
RemediationAI
No vendor-released patch has been identified at time of analysis: the vendor was contacted early about the disclosure and did not respond, so there is no confirmed fixed extension version and no vendor advisory URL to cite. The most reliable mitigation is to uninstall or disable the Coze Scraper extension (version 2.0.2 or earlier) until the maintainer ships a version that validates the sender's origin, accepting the loss of the extension's scraping functionality as the trade-off. If the extension must stay enabled, Chrome enterprise policy can block or force-remove it by extension ID, and administrators can use allowlisting so only reviewed extensions run; note that this requires knowing the extension ID and maintaining the policy across managed browsers. If you are the maintainer, the fix is to check the message sender's origin (for example via the event.sender/event.origin values available to chrome.runtime.onMessageExternal) against an allowlist and reject messages from untrusted origins before touching body.url, body.urls, paginationConfig, xPathConfig, or xPaths; narrowing the externally_connectable matches in the manifest to specific trusted origins is a defence-in-depth alternative, but it reduces intended integrations. Given that exploitation requires the user to visit an attacker-controlled page, restricting user browsing to trusted sites and enforcing strong web filtering reduces exposure, though it is not a complete control. Additional technical detail and proof-of-concept context are documented at https://github.com/xryj920/chrome_extensions/blob/main/Coze%20Scraper%202.0.2%20Unrestricted%20External%20Message%20Handler%20Allows%20Website-Triggered%20Arbitrary%20URL%20Scraping and https://vuldb.com/vuln/409003.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Chrome extensions can opt in to receiving messages from ordinary web pages via the externally_connectable manifest key, which exposes the chrome.runtime.onMessageExternal event. In the Coze Scraper extension this listener is implemented in static/background/index.js and consumes caller-supplied fields (body.url, body.urls, paginationConfig, xPathConfig, xPaths) to configure scraping jobs, but it never validates that the sending origin is a trusted site and processes the request regardless of who sent it. That absence of an origin/authorization check is CWE-862 (Missing Authorization): the message handler effectively treats any web origin as an authorized client, so a malicious page can coerce the extension into fetching arbitrary URLs and returning scraped content. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P) and the independent CVSS 3.1 assessment (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N) agree that the attack is network-delivered, requires no authentication, requires user interaction (UI:P/UI:R), and produces only low confidentiality impact inside the extension's scope with no integrity, availability, or subsequent-system impact. There is no privilege escalation or code execution primitive; the effect is confined to attacker-directed scraping and data exfiltration from pages the user could already load.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
Any website can reach the unauthenticated external message handler (PR:N) but a victim must load the attacker page (UI:R); impact is limited to attacker-directed scraping, so C:L, I:N, A:N.
Primary rating from Vendor (vuldb).
CVSS VectorVendor: vuldb
DescriptionCVE.org
A vulnerability was detected in ByteDance Coze Scraper Extension up to 2.0.2. Affected by this vulnerability is the function chrome.runtime.onMessageExternal.addListener of the file static/background/index.js of the component External Message Handler. The manipulation of the argument body.url/paginationConfig/xPathConfig/body.urls/xPaths results in missing authorization. The attack can be launched remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-85729
GHSA-8fch-9xj9-6929
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB