{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-22928 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-22928 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-22928 is a critical vulnerability in n/a, published on 20 Jan 2022. 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-22928 and fix it if it is affected.\n\nWhat it is: CVE-2022-22928 is a critical vulnerability in n/a, published on 20 Jan 2022. 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-22928 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-22928/ (Markdown: https://insights.sbomify.com/CVE-2022-22928/index.md)","id":"CVE-2022-22928","markdown":"https://insights.sbomify.com/CVE-2022-22928/index.md","name":"CVE-2022-22928","record":{"aliases":["GHSA-w5jp-93v7-x9q3"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"MCMS content management","requires_auth":"none","summary":"Attackers can exploit a hardcoded Shiro key in MCMS to execute arbitrary code, requiring immediate patching by administrators.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mcms","vendor":"mingsoft"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"MCMS v5.2.4 was discovered to have a hardcoded shiro-key, allowing attackers to exploit the key and execute arbitrary 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":"Hardcoded credentials in n/a","id":"CVE-2022-22928","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Arbitrary File Upload in Mingsoft MCMS","id":"CVE-2022-22929"},"packages":[],"prev":{"headline":"Weak cryptography in n/a","id":"CVE-2022-22922"},"products":["n/a"],"published":"2022-01-20","related":[{"cvss_score":9.8,"headline":"MCMS vulnerable SQL injection via the content_title parameter","id":"CVE-2025-56316","kev_date_added":null,"published":"2025-10-17"},{"cvss_score":9.8,"headline":"MCMS allows arbitrary file uploads in the ueditor component","id":"CVE-2025-29287","kev_date_added":null,"published":"2025-04-21"},{"cvss_score":9.8,"headline":"Mingsoft MCMS SQL injection","id":"CVE-2023-50578","kev_date_added":null,"published":"2023-12-30"},{"cvss_score":9.8,"headline":"Ming-Soft MCMS vulnerable to SQL injection","id":"CVE-2020-20913","kev_date_added":null,"published":"2023-04-04"},{"cvss_score":9.8,"headline":"Mingsoft MCMS SQL injection vulnerability in /mdiy/page/verify URI via fieldName parameter","id":"CVE-2022-36272","kev_date_added":null,"published":"2022-08-16"},{"cvss_score":9.8,"headline":"Mingsoft MCMS SQL injection vulnerability in /mdiy/model/delete URI via models List","id":"CVE-2022-36599","kev_date_added":null,"published":"2022-08-16"},{"cvss_score":9.8,"headline":"Unrestricted Upload of File with Dangerous Type in MCMS","id":"CVE-2022-31943","kev_date_added":null,"published":"2022-07-01"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Attackers can exploit a hardcoded Shiro key in MCMS to execute arbitrary code, requiring immediate patching by administrators.","url":"https://insights.sbomify.com/CVE-2022-22928/"}