Security readout for executives and security teams
Plain-English summary
CVE-2018-10000 concerns an old Chrome extension flaw. If users had Video Downloader professional before 2018-04-05, malicious web content could potentially abuse the extension to run unwanted script across sites. Current risk depends on whether the extension still exists in managed or legacy browser profiles.
Executive priority
Treat as a targeted endpoint hygiene issue, not an enterprise-wide emergency by default. Prioritize confirmation in managed Chrome fleets and remove unnecessary extension use, especially on systems handling sensitive web applications or credentials.
Technical view
The CVE describes Universal XSS in Video Downloader professional for Chrome before 2018-04-05, tied to handling of a link64_msgAddLinks event. The bundle provides no CVSS score, CWE, CPE, detailed version list, or vendor advisory beyond the Project Zero reference.
Likely exposure
Exposure is limited to Chrome environments where Video Downloader professional was installed in an affected pre-2018-04-05 state. Modern exposure is most plausible through unmanaged endpoints, stale browser profiles, archived images, or extension policies that reinstall old or sideloaded copies.
Exploitation context
The provided bundle does not show CISA KEV listing or active exploitation. The issue is serious because UXSS can cross normal site boundaries through extension behavior, but the public evidence supplied here is sparse and should not be treated as proof of exploitation in the wild.
Researcher notes
The source data is thin: no CVSS, CPE, CWE, exploit narrative, or detailed fix note is included. Analysis should stay constrained to the named Chrome extension, the pre-2018-04-05 affected window, and the referenced Project Zero issue.
Mitigation direction
- Inventory Chrome extension deployments for Video Downloader professional.
- Remove the extension where it is not business-required.
- Ensure any retained copy is newer than 2018-04-05.
- Block sideloaded or unapproved Chrome extensions by policy.
- Check vendor or Chrome Web Store guidance for current status.
Validation and detection
- Review managed Chrome extension policy for this extension.
- Inspect endpoint browser profiles for installed or legacy copies.
- Confirm installation source, version, and update date.
- Check EDR or asset data for affected Chrome profiles.
- Document exceptions for any retained installation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2018-10000 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://bugs.chromium.org/p/project-zero/issues/detail?id=1555CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.