{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-46101 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-46101 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-46101 is a high-severity code injection vulnerability in n/a, published on 22 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-46101 and fix it if it is affected.\n\nWhat it is: CVE-2022-46101 is a high-severity code injection vulnerability in n/a, published on 22 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-46101 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-46101/ (Markdown: https://insights.sbomify.com/CVE-2022-46101/index.md)","id":"CVE-2022-46101","markdown":"https://insights.sbomify.com/CVE-2022-46101/index.md","name":"CVE-2022-46101","record":{"aliases":["GHSA-76w3-2xmj-8wr3"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"AyaCMS","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary code in AyaCMS via malicious input in the ust_sql.inc.php file, posing a critical risk to web application integrity.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ayacms","vendor":"ayacms_project"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"AyaCMS v3.1.2 was found to have a code flaw in the ust_sql.inc.php file, which allows attackers to cause command execution by inserting malicious code.","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":"Code injection in n/a","id":"CVE-2022-46101","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"File upload in n/a","id":"CVE-2022-46102"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2022-46096"},"products":["n/a"],"published":"2022-12-22","related":[{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2022-46102","kev_date_added":null,"published":"2022-12-22"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2022-47926","kev_date_added":null,"published":"2022-12-22"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2022-45550","kev_date_added":null,"published":"2022-12-07"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2022-43074","kev_date_added":null,"published":"2022-11-10"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2022-45548","kev_date_added":null,"published":"2022-12-06"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2020-23686","kev_date_added":null,"published":"2021-11-02"}],"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":"total"},"state":"PUBLISHED","updated":"2025-04-15","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code in AyaCMS via malicious input in the ust_sql.inc.php file, posing a critical risk to web application integrity.","url":"https://insights.sbomify.com/CVE-2022-46101/"}