CVE-2012-0309 json
Cross-site scripting (XSS) vulnerability in Cogent DataHub 7.1.2 and earlier, Cascade DataHub 6.4.20 and earlier, and OPC DataHub 6.4.20 an…
published 2012-01-13 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-0345
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 0
- none known
Summary
Cross-site scripting (XSS) vulnerability in Cogent DataHub 7.1.2 and earlier, Cascade DataHub 6.4.20 and earlier, and OPC DataHub 6.4.20 and earlier allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-12-016-01 updated cvss 4.3
Cogent DataHub XSS and CRLF
-
Cogent Real-Time Systems Cascade DataHub <=6.4.20 Cogent Real-Time Systems Cogent DataHub <=7.1.2 Cogent Real-Time Systems OPC DataHub <=6.4.20affected: mitigation
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
Exploit prediction
1.29% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
jvndb.jvn.jp
/jvndb/JVNDB-2012-000001
third-party-advisory
-
securityfocus.com
/bid/51375
vdb-entry
- cogentdatahub.com /ReleaseNotes.html
- us-cert.gov /control_systems/pdf/ICSA-12-016-01.pdf
-
secunia.com
/advisories/47525
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/72305
vdb-entry
-
jvn.jp
/en/jp/JVN12983784/index.html
third-party-advisory
-
secunia.com
/advisories/47496
third-party-advisory
Sources
- CVE List CVE-2012-0309
- NVD CVE-2012-0309
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.