CVE-2007-2379 json
The jQuery framework exchanges data using JavaScript Object Notation (JSON) without an associated protection scheme, which allows remote at…
published 2007-04-30 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-2374
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.8%
- EPSS 2.8% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known
Summary
The jQuery framework exchanges data using JavaScript Object Notation (JSON) without an associated protection scheme, which allows remote attackers to obtain the data via a web page that retrieves the data through a URL in the SRC attribute of a SCRIPT element and captures the data using other JavaScript code, aka "JavaScript Hijacking."
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-22-097-01 updated cvss 5.3
Pepperl+Fuchs WirelessHART-Gateway
-
Pepperl+Fuchs WHA-GW-F2D2-0-AS- Z2-ETH 3.0.7, 3.0.8, 3.0.9 Pepperl+Fuchs WHA-GW-F2D2-0-AS- Z2-ETH.EIP 3.0.7, 3.0.8, 3.0.9affected: mitigation “Minimize network exposure for affected products and ensure they are not accessible via the Internet.” cert.vde.com
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
2.77% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
fortifysoftware.com
/servlet/downloads/public/JavaScript_Hijacking.pdf
third-party-advisory, url-repurposed
-
osvdb.org
/43320
vdb-entry, broken-link
-
security.netapp.com
/advisory/ntap-20190416-0007/
third-party-advisory
Sources
- CVE List CVE-2007-2379
- NVD CVE-2007-2379
Fencer Vulns 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.