{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-24036 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-24036 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-24036 is a high-severity unsafe deserialization vulnerability in n/a, published on 4 Mar 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-24036 and fix it if it is affected.\n\nWhat it is: CVE-2020-24036 is a high-severity unsafe deserialization vulnerability in n/a, published on 4 Mar 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-24036 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-2020-24036/ (Markdown: https://insights.sbomify.com/CVE-2020-24036/index.md)","id":"CVE-2020-24036","markdown":"https://insights.sbomify.com/CVE-2020-24036/index.md","name":"CVE-2020-24036","record":{"aliases":["GHSA-xvr9-jr9p-grf3"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"ForkCMS","requires_auth":"low_privilege","summary":"Authenticated attackers can execute malicious code via PHP object injection in the ForkCMS backend Ajax endpoint.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"fork_cms","vendor":"fork-cms"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","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-502","name":"Deserialization of Untrusted Data"}],"description":"PHP object injection in the Ajax endpoint of the backend in ForkCMS below version 5.8.3 allows an authenticated remote user to execute 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":false,"headline":"Deserialization in n/a","id":"CVE-2020-24036","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2020"},"n_packages":0,"n_references":4,"next":{"headline":"Information disclosure in n/a","id":"CVE-2020-24038"},"packages":[],"prev":{"headline":"Deserialization in n/a","id":"CVE-2020-24034"},"products":["n/a"],"published":"2021-03-04","related":[{"cvss_score":9.8,"headline":"Spoon Library as used in Fork CMS allows PHP object injection","id":"CVE-2019-15521","kev_date_added":null,"published":"2019-08-26"},{"cvss_score":9.6,"headline":"SQL Injection in forkcms/forkcms","id":"CVE-2022-0153","kev_date_added":null,"published":"2022-03-24"},{"cvss_score":9,"headline":"SQL injection through marking blog comments on bulk as spam in forkcms/forkcms","id":"CVE-2022-1064","kev_date_added":null,"published":"2022-03-25"},{"cvss_score":8.8,"headline":"Arbitrary file upload in Fork CMS","id":"CVE-2021-28931","kev_date_added":null,"published":"2021-07-07"},{"cvss_score":8.8,"headline":"Cross-Site Request Forgery in forkcms","id":"CVE-2020-23264","kev_date_added":null,"published":"2021-05-06"},{"cvss_score":8.8,"headline":"Cross-Site Request Forgery in ForkCMS","id":"CVE-2020-23960","kev_date_added":null,"published":"2021-01-11"}],"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":"2026-07-09","vendors":["n/a"]},"summary":"Authenticated attackers can execute malicious code via PHP object injection in the ForkCMS backend Ajax endpoint.","url":"https://insights.sbomify.com/CVE-2020-24036/"}