Skip to content
Fencer Intel
medium 5.8

CVE-2013-6127 json

The SUPERGRIDLib.SuperGrid ActiveX control in SuperGrid.ocx before 65.30.30000.10002 in WellinTech KingView before 6.53 does not properly r…

published 13y ago modified 4mo ago also EUVD-2013-5956

cvss
5.8
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
13.9%
EPSS 13.9% chance of exploitation in 30 days, percentile 96%
public exploits
1
Exploit-DB

Summary

The SUPERGRIDLib.SuperGrid ActiveX control in SuperGrid.ocx before 65.30.30000.10002 in WellinTech KingView before 6.53 does not properly restrict ReplaceDBFile method calls, which allows remote attackers to create or overwrite arbitrary files, and subsequently execute arbitrary programs, via the two pathname arguments, as demonstrated by a directory traversal attack.

Is CVE-2013-6127 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-13-295-01 updated cvss 5.8

WellinTech KingView ActiveX Vulnerabilities

  • WellinTech KingView <6.53
    affected: mitigation “KChartXY.ocx Version number: 65.30.30000.10002 (http://www.kingview.com/en/downloads/Downloads/KChartXY.rar)”

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Timeline

  1. First public exploit (EDB-28084)
  2. Published

Exploit prediction

13.85% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-28084 KingView 6.53 - 'SuperGrid' Insecure ActiveX Control local, 2013-09-04

CVSS scores

assigned by version score vector
NVD 2.0 5.8 AV:N/AC:M/Au:N/C:N/I:P/A:P

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.