{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-46252 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-46252 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-46252 is a medium-severity cross-site scripting vulnerability in squidex, published on 7 Nov 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-46252 and fix it if it is affected.\n\nWhat it is: CVE-2023-46252 is a medium-severity cross-site scripting vulnerability in squidex, published on 7 Nov 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-46252 in the wild and no public exploit code.\n\nAffected product: squidex. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-46252/ (Markdown: https://insights.sbomify.com/CVE-2023-46252/index.md)","id":"CVE-2023-46252","markdown":"https://insights.sbomify.com/CVE-2023-46252/index.md","name":"CVE-2023-46252","record":{"aliases":["GHSA-7q4f-fprr-5jw8"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Headless CMS","requires_auth":"none","summary":"Attackers can execute arbitrary scripts in victim browsers via a missing origin check in the postMessage handler of the Squidex editor SDK.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"squidex","vendor":"squidex.io"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Squidex is an open source headless CMS and content management hub. Affected versions are missing origin verification in a postMessage handler which introduces a Cross-Site Scripting (XSS) vulnerability. The editor-sdk.js file defines three different class-like functions, which employ a global message event listener: SquidexSidebar, SquidexWidget, and SquidexFormField. The registered event listener takes some action based on the type of the received message. For example, when the SquidexFormField receives a message with the type valueChanged, the value property is updated. The SquidexFormField class is for example used in the editor-editorjs.html file, which can be accessed via the public wwwroot folder. It uses the onValueChanged method to register a callback function, which passes the value provided from the message event to the editor.render. Passing an attacker-controlled value to this function introduces a Cross-Site Scripting (XSS) vulnerability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Cross-Site Scripting (XSS) via postMessage Handler in Squidex","id":"CVE-2023-46252","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Remote code execution in Squidex","id":"CVE-2023-46253"},"packages":[],"prev":{"headline":"Visual editor persistent Cross-site Scripting (XSS) in MyBB","id":"CVE-2023-46251"},"products":["squidex"],"published":"2023-11-07","related":[{"cvss_score":9.1,"headline":"Squidex has Server-Side Request Forgery (SSRF) Issue in Webhook Configuration","id":"CVE-2026-24736","kev_date_added":null,"published":"2026-01-27"},{"cvss_score":9.1,"headline":"Remote code execution in Squidex","id":"CVE-2023-46253","kev_date_added":null,"published":"2023-11-07"},{"cvss_score":6.8,"headline":"Cross-Site Request Forgery (CSRF) in squidex/squidex","id":"CVE-2023-0642","kev_date_added":null,"published":"2023-02-02"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2023-24278","kev_date_added":null,"published":"2023-03-18"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2023-46857","kev_date_added":null,"published":"2023-12-07"},{"cvss_score":5.4,"headline":"Stored Cross-site Scripting in Squidex","id":"CVE-2023-46744","kev_date_added":null,"published":"2023-11-07"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-04","vendors":["Squidex"]},"summary":"Attackers can execute arbitrary scripts in victim browsers via a missing origin check in the postMessage handler of the Squidex editor SDK.","url":"https://insights.sbomify.com/CVE-2023-46252/"}