{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-46839 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-46839 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-46839 is a critical vulnerability in JS Help Desk – Best Help Desk \u0026 Support Plugin, published on 5 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-46839 and fix it if it is affected.\n\nWhat it is: CVE-2022-46839 is a critical vulnerability in JS Help Desk – Best Help Desk \u0026 Support Plugin, published on 5 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-46839 in the wild and no public exploit code.\n\nAffected product: JS Help Desk – Best Help Desk \u0026 Support Plugin. 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-46839/ (Markdown: https://insights.sbomify.com/CVE-2022-46839/index.md)","id":"CVE-2022-46839","markdown":"https://insights.sbomify.com/CVE-2022-46839/index.md","name":"CVE-2022-46839","record":{"aliases":["GHSA-m3fq-v9fh-gg5p"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can upload malicious files to the JS Help Desk WordPress plugin, potentially leading to remote code execution.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[{"product":"js_help_desk","vendor":"wiselyhub"}],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"Unrestricted Upload of File with Dangerous Type vulnerability in JS Help Desk JS Help Desk – Best Help Desk \u0026 Support Plugin.This issue affects JS Help Desk – Best Help Desk \u0026 Support Plugin: from n/a through 2.7.1.","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":"WordPress JS Help Desk – Best Help Desk \u0026 Support Plugin Plugin \u003c= 2.7.1 is vulnerable to Arbitrary File Upload","id":"CVE-2022-46839","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress JS Help Desk plugin \u003c= 2.7.1 - Broken Access Control","id":"CVE-2022-46840"},"packages":[],"prev":{"headline":"WordPress JS Help Desk plugin \u003c= 2.7.1 - Unauthenticated Settings Change Vulnerability","id":"CVE-2022-46838"},"products":["JS Help Desk – Best Help Desk \u0026 Support Plugin"],"published":"2024-01-05","related":[{"cvss_score":9.3,"headline":"WordPress JS Help Desk – Best Help Desk \u0026 Support Plugin \u003c= 2.8.1 is vulnerable to SQL Injection","id":"CVE-2023-50839","kev_date_added":null,"published":"2023-12-28"},{"cvss_score":7.5,"headline":"Information disclosure in JS Help Desk – AI-Powered Support \u0026 Ticketing System","id":"CVE-2024-13606","kev_date_added":null,"published":"2025-02-13"},{"cvss_score":5.4,"headline":"WordPress JS Help Desk plugin \u003c= 2.7.1 is vulnerable to Cross Site Request Forgery (CSRF)","id":"CVE-2022-46842","kev_date_added":null,"published":"2023-02-02"},{"cvss_score":5.3,"headline":"WordPress JS Help Desk plugin \u003c= 2.8.3 - Broken Access Control vulnerability","id":"CVE-2024-31273","kev_date_added":null,"published":"2024-06-09"}],"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-28","vendors":["JS Help Desk"]},"summary":"Attackers can upload malicious files to the JS Help Desk WordPress plugin, potentially leading to remote code execution.","url":"https://insights.sbomify.com/CVE-2022-46839/"}