Security readout for executives and security teams
Plain-English summary
Cobub Razor 0.7.2 lets unauthenticated users modify a channel field in a way that can later run malicious script in an administrator’s browser. For organizations still running this older analytics platform, the business risk is admin-session abuse, data exposure, or follow-on changes made through the admin UI.
Executive priority
Prioritize remediation if Cobub Razor is still deployed and reachable. The issue is old, but unauthenticated stored XSS against administrators can create meaningful account and data risk.
Technical view
The CVE describes unauthenticated access to /index.php?/manage/channel/modifychannel. A crafted channel name is stored and later triggers XSS when an admin views /index.php?/manage/channel. Public references include an Exploit-DB entry and a GitHub issue, but the bundle provides no CVSS score, CWE mapping, or named fixed version.
Likely exposure
Exposure is limited to systems running Western Bridge Cobub Razor 0.7.2, especially if the application or management paths are internet-accessible. The source bundle does not identify other affected versions or products.
Exploitation context
A public Exploit-DB reference exists, so proof-of-concept detail has been published. The CVE is not marked KEV, and the provided sources do not show active exploitation in the wild.
Researcher notes
Evidence is concise and product-specific. The bundle supports unauthenticated stored XSS in Cobub Razor 0.7.2, public exploit availability, and no KEV listing. It does not provide CVSS, confirmed patch details, or affected-version range beyond 0.7.2.
Mitigation direction
- Identify any Cobub Razor 0.7.2 deployments and ownership.
- Check vendor or project guidance for a fixed version or workaround.
- Restrict external access to Cobub Razor management paths.
- Retire or isolate the application if no supported fix exists.
- Review stored channel data for suspicious or unexpected entries.
Validation and detection
- Confirm whether Cobub Razor 0.7.2 is present in the environment.
- Verify management channel modification requires authentication.
- Review logs for unauthenticated requests to the affected path.
- Check whether channel names are safely encoded in admin views.
- Confirm any compensating access controls cover public and internal entry points.
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-7746 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
- 44416CVE reference · exploit, x_refsource_EXPLOIT-DB
- https://github.com/cobub/razor/issues/161CVE 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.