{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-46381 exists.","fix":"No fix has been published for CVE-2022-46381 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-46381 is a medium-severity cross-site scripting vulnerability in n/a, published on 13 Dec 2022. 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-46381 and fix it if it is affected.\n\nWhat it is: CVE-2022-46381 is a medium-severity cross-site scripting vulnerability in n/a, published on 13 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-46381 exists.\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-46381/ (Markdown: https://insights.sbomify.com/CVE-2022-46381/index.md)","id":"CVE-2022-46381","markdown":"https://insights.sbomify.com/CVE-2022-46381/index.md","name":"CVE-2022-46381","record":{"aliases":["GHSA-wwh4-qv5c-5223"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Linear eMerge E3-Series","requires_auth":"none","summary":"Attackers can inject malicious scripts via the type parameter in Linear eMerge E3-Series devices, potentially compromising user sessions or data.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"linear_emerge_e3_access_control_firmware","vendor":"niceforyou"}],"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":"Certain Linear eMerge E3-Series devices are vulnerable to XSS via the type parameter (e.g., to the badging/badge_template_v0.php component). This affects 0.32-08f, 0.32-07p, 0.32-07e, 0.32-09c, 0.32-09b, 0.32-09a, and 0.32-08e.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2022-12-14","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":1,"refs":[{"date":"2022-12-14T20:07:52Z","kind":"github_poc","ref":"https://github.com/amitlttwo/CVE-2022-46381","stars":0,"title":null},{"date":null,"kind":"nuclei","ref":"http/cves/2022/CVE-2022-46381.yaml","stars":null,"title":"Linear eMerge E3-Series - Cross-Site Scripting"}],"tier":"weaponised"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2022-46381","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in n/a","id":"CVE-2022-46382"},"packages":[],"prev":{"headline":"Denial of service in uC-FTPs","id":"CVE-2022-46378"},"products":["n/a"],"published":"2022-12-13","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-38627","kev_date_added":null,"published":"2023-01-03"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2022-38628","kev_date_added":null,"published":"2022-12-13"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2022-42710","kev_date_added":null,"published":"2023-01-03"}],"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":"MIT","name":"Nuclei templates"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-22","vendors":["n/a"]},"summary":"Attackers can inject malicious scripts via the type parameter in Linear eMerge E3-Series devices, potentially compromising user sessions or data.","url":"https://insights.sbomify.com/CVE-2022-46381/"}