{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-48110 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-48110 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-48110 is a medium-severity cross-site scripting vulnerability in n/a, published on 13 Feb 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-48110 and fix it if it is affected.\n\nWhat it is: CVE-2022-48110 is a medium-severity cross-site scripting vulnerability in n/a, published on 13 Feb 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-48110 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2022-48110/ (Markdown: https://insights.sbomify.com/CVE-2022-48110/index.md)","id":"CVE-2022-48110","markdown":"https://insights.sbomify.com/CVE-2022-48110/index.md","name":"CVE-2022-48110","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"configuration_change","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"CKEditor 5","requires_auth":"none","summary":"Cross-site scripting in CKEditor 5 widget requires integrators to configure security settings correctly to prevent exploitation.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ckeditor","vendor":"ckeditor"}],"cvss":{"score":6.1,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"CKSource CKEditor 5 35.4.0 was discovered to contain a cross-site scripting (XSS) vulnerability via the Full Featured CKEditor5 widget. NOTE: the vendor's position is that this is not a vulnerability. The CKEditor 5 documentation discusses that it is the responsibility of an integrator (who is adding CKEditor 5 functionality to a website) to choose the correct security settings for their use case. Also, safe default values are established (e.g., config.htmlEmbed.showPreviews is false).","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2023-04-05","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2023-04-05","kind":"exploitdb","ref":"51260","stars":null,"title":"CKEditor 5 35.4.0 - Cross-Site Scripting (XSS)"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2022-48110","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2022-48111"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2022-48108"},"products":["n/a"],"published":"2023-02-13","related":[{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2023-31541","kev_date_added":null,"published":"2023-06-13"},{"cvss_score":8.2,"headline":"Advanced Content Filter (ACF) vulnerability allowing to execute JavaScript code using malformed HTML","id":"CVE-2021-41164","kev_date_added":null,"published":"2021-11-17"},{"cvss_score":8.2,"headline":"HTML comments vulnerability allowing to execute JavaScript code","id":"CVE-2021-41165","kev_date_added":null,"published":"2021-11-17"},{"cvss_score":7.6,"headline":"Cross-site scripting in ckeditor via abuse of undo functionality","id":"CVE-2021-32808","kev_date_added":null,"published":"2021-08-12"},{"cvss_score":7.5,"headline":"Missing authorization in CKEditor Drupal module","id":"CVE-2011-4972","kev_date_added":null,"published":"2019-11-13"},{"cvss_score":7.3,"headline":"Execution of JavaScript code using malformed HTML in ckeditor","id":"CVE-2021-37695","kev_date_added":null,"published":"2021-08-12"},{"cvss_score":6.8,"headline":"Code injection in n/a","id":"CVE-2012-2067","kev_date_added":null,"published":"2012-09-05"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-24","vendors":["n/a"]},"summary":"Cross-site scripting in CKEditor 5 widget requires integrators to configure security settings correctly to prevent exploitation.","url":"https://insights.sbomify.com/CVE-2022-48110/"}