CVE-2026-41886
- Source
- https://cve.org/CVERecord?id=CVE-2026-41886
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-41886.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-41886
- Aliases
- Published
- 2026-05-08T15:45:23.262Z
- Modified
- 2026-07-15T01:48:54.057155124Z
- Severity
-
- 7.5 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:L CVSS Calculator
- Summary
- locize Client SDK: Cross-origin DOM XSS & Handler Hijack Through Missing e.origin Validation in InContext Editor
- Details
-
locize is a localization platform that connects code and i18n setup. Prior to version 4.0.21, the locize client SDK registers a window.addEventListener("message", …) handler that dispatches to registered internal handlers (editKey, commitKey, commitKeys, isLocizeEnabled, requestInitialize, …) without validating event.origin. The pre-patch listener in src/api/postMessage.js gates dispatch on event.data.sender === "i18next-editor-frame" — that value sits inside the attacker-controlled message payload, not the browser-enforced origin. Any web page that could embed or be embedded by a locize-enabled host — an iframe on a third-party page, a window.open-ed victim, a parent frame reaching down — could send a crafted postMessage and trigger the internal handlers. This issue has been patched in version 4.0.21.
- Database specific
{ "cwe_ids": [ "CWE-346", "CWE-79" ], "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/41xxx/CVE-2026-41886.json", "cna_assigner": "GitHub_M" }- References