{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-44002 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-44002 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-44002 is a medium-severity cross-site scripting vulnerability in n/a, published on 16 Nov 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-44002 and fix it if it is affected.\n\nWhat it is: CVE-2022-44002 is a medium-severity cross-site scripting vulnerability in n/a, published on 16 Nov 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: There is no known exploitation of CVE-2022-44002 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-44002/ (Markdown: https://insights.sbomify.com/CVE-2022-44002/index.md)","id":"CVE-2022-44002","markdown":"https://insights.sbomify.com/CVE-2022-44002/index.md","name":"CVE-2022-44002","record":{"aliases":["GHSA-ffc5-94vf-24gj"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"BACKCLICK Professional","requires_auth":"none","summary":"Attackers can inject malicious scripts into BACKCLICK Professional via insufficient output encoding, potentially leading to session hijacking or code execution.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"backclick","vendor":"backclick"}],"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":"An issue was discovered in BACKCLICK Professional 5.9.63. Due to insufficient output encoding of user-supplied data, the web application is vulnerable to cross-site scripting (XSS) at various locations.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2022-44002","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2022-44003"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2022-44001"},"products":["n/a"],"published":"2022-11-16","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2022-44001","kev_date_added":null,"published":"2022-11-17"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2022-43999","kev_date_added":null,"published":"2022-11-16"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2022-44000","kev_date_added":null,"published":"2022-11-16"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-44003","kev_date_added":null,"published":"2022-11-16"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2022-44004","kev_date_added":null,"published":"2022-11-16"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2022-44006","kev_date_added":null,"published":"2022-11-16"},{"cvss_score":8.8,"headline":"Other in n/a","id":"CVE-2022-44007","kev_date_added":null,"published":"2022-11-16"}],"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":"2025-04-30","vendors":["n/a"]},"summary":"Attackers can inject malicious scripts into BACKCLICK Professional via insufficient output encoding, potentially leading to session hijacking or code execution.","url":"https://insights.sbomify.com/CVE-2022-44002/"}