{"answers":{"affected":"2 open source packages ship an affected version, including tribalsystems/zenario. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-18420 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-18420 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-18420 is a high-severity vulnerability in n/a, published on 19 Oct 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-18420 and fix it if it is affected.\n\nWhat it is: CVE-2018-18420 is a high-severity vulnerability in n/a, published on 19 Oct 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-18420 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- tribalsystems/zenario (Packagist): affected all versions; no fix listed\n- tribalsystems/zenario (Packagist): affected all versions; no fix listed\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-2018-18420/ (Markdown: https://insights.sbomify.com/CVE-2018-18420/index.md)","id":"CVE-2018-18420","markdown":"https://insights.sbomify.com/CVE-2018-18420/index.md","name":"CVE-2018-18420","record":{"aliases":["GHSA-22cq-xxr9-jrrv"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Zenario CMS","requires_auth":"none","summary":"A Cross-Site Request Forgery vulnerability in Zenario CMS allows attackers to perform unauthorized actions on behalf of authenticated users.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"zenario","vendor":"tribalsystems"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Cross-Site Request Forgery (CSRF) vulnerability was discovered in the 8.3 version of Zenario Content Management System via the admin/organizer.ajax.php?path=zenario__content%2Fpanels%2Fcontent URI.","ecosystems":["Packagist"],"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":"Zenario CMS vulnerable to CSRF","id":"CVE-2018-18420","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"csrf","year":"2018"},"n_packages":2,"n_references":1,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2018-18422"},"packages":[{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":[],"package":"tribalsystems/zenario","purl":null,"source":"GHSA-22cq-xxr9-jrrv"},{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":[],"package":"tribalsystems/zenario","purl":"pkg:composer/tribalsystems/zenario","source":"GHSA-22cq-xxr9-jrrv"}],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-18419"},"products":["n/a"],"published":"2018-10-19","related":[{"cvss_score":9.8,"headline":"Zenario CMS is vulnerable to Remote Code Execution (RCE).","id":"CVE-2022-44136","kev_date_added":null,"published":"2022-11-30"},{"cvss_score":9.1,"headline":"SQL Injection in tribalsystems/zenario","id":"CVE-2021-26830","kev_date_added":null,"published":"2021-04-16"},{"cvss_score":8.8,"headline":"SQL Injection in Zenario 7.1-7.6","id":"CVE-2018-5960","kev_date_added":null,"published":"2018-01-22"},{"cvss_score":7.2,"headline":"Unrestricted Upload of File with Dangerous Type in Zenario CMS","id":"CVE-2021-42171","kev_date_added":null,"published":"2022-03-14"},{"cvss_score":7.2,"headline":"File upload restriction bypass in Zenario CMS","id":"CVE-2022-23043","kev_date_added":null,"published":"2022-02-22"},{"cvss_score":5.4,"headline":"Zenario CMS Cross-site Scripting vulnerability","id":"CVE-2023-44769","kev_date_added":null,"published":"2023-10-24"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-05","vendors":["n/a"]},"summary":"A Cross-Site Request Forgery vulnerability in Zenario CMS allows attackers to perform unauthorized actions on behalf of authenticated users.","url":"https://insights.sbomify.com/CVE-2018-18420/"}