{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-27333 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-27333 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-27333 is a high-severity missing authorization vulnerability in Idccms Idccms, published on 21 Mar 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-27333 and fix it if it is affected.\n\nWhat it is: CVE-2022-27333 is a high-severity missing authorization vulnerability in Idccms Idccms, published on 21 Mar 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-27333 in the wild and no public exploit code.\n\nAffected product: Idccms Idccms. 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-27333/ (Markdown: https://insights.sbomify.com/CVE-2022-27333/index.md)","id":"CVE-2022-27333","markdown":"https://insights.sbomify.com/CVE-2022-27333/index.md","name":"CVE-2022-27333","record":{"aliases":["GHSA-g3m8-rmp8-jhwv"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"idcCMS","requires_auth":"none","summary":"Attackers can arbitrarily delete the install.lock file, resetting CMS settings and data due to missing authorization checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"idccms","vendor":"idccms"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[],"description":"idcCMS v1.10 was discovered to contain an issue which allows attackers to arbitrarily delete the install.lock file, resulting in a reset of the CMS settings and data.","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":"Missing authorization in n/a","id":"CVE-2022-27333","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"idccms:idccms","products":["idccms:idccms"],"type":"missing_authorization","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Code injection in n/a","id":"CVE-2022-27336"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2022-27332"},"products":["n/a"],"published":"2022-03-21","related":[{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2024-40329","kev_date_added":null,"published":"2024-07-10"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2024-40331","kev_date_added":null,"published":"2024-07-10"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2024-40333","kev_date_added":null,"published":"2024-07-10"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2024-40334","kev_date_added":null,"published":"2024-07-10"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2024-40036","kev_date_added":null,"published":"2024-07-09"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2024-39022","kev_date_added":null,"published":"2024-07-05"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2024-39023","kev_date_added":null,"published":"2024-07-05"}],"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":"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 arbitrarily delete the install.lock file, resetting CMS settings and data due to missing authorization checks.","url":"https://insights.sbomify.com/CVE-2022-27333/"}