CVE-2020-11611 json
Open Redirect in xdLocalStorage
published 6y ago modified 4mo ago also GHSA-c6c4-jmqx-3r33 , EUVD-2021-2502
- cvss
- 6.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 61%
- public exploits
- 0
- none known
Summary
An issue was discovered in xdLocalStorage through 2.0.5. The buildMessage() function in xdLocalStorage.js specifies the wildcard (*) as the targetOrigin when calling the postMessage() function on the iframe object. Therefore any domain that is currently loaded within the iframe can receive the messages that the client sends.
Is CVE-2020-11611 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.94% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- grimhacker.com https://grimhacker.com/exploiting-xdlocalstorage-localstorage-and-postmessage/#Missing-TargetOrigin-Client referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:P/I:P/A:N |
| GitHub | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | xdlocalstorage | <=2.0.5 |
no fix listed |
Classification
- Weakness
-
- CWE-601 URL Redirection to Untrusted Site
References
-
grimhacker.com
/exploiting-xdlocalstorage-localstorage-and-postmessage/#Missing-TargetOrigin-Client
web, exploit, third-party-advisory
-
github.com
/ofirdagan/cross-domain-local-storage
web, product, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-11611
advisory
Sources
- CVE List CVE-2020-11611
- GitHub Advisory GHSA-c6c4-jmqx-3r33
- NVD CVE-2020-11611
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.