{"answers":{"affected":"2 open source packages ship an affected version, including forkcms/forkcms. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-5215 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-5215 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-5215 is a medium-severity cross-site scripting vulnerability in n/a, published on 4 Jan 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-5215 and fix it if it is affected.\n\nWhat it is: CVE-2018-5215 is a medium-severity cross-site scripting vulnerability in n/a, published on 4 Jan 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-5215 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- forkcms/forkcms (Packagist): affected all versions up to 5.0.7; no fix listed\n- forkcms/forkcms (Packagist): affected all versions up to 5.0.7; 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-5215/ (Markdown: https://insights.sbomify.com/CVE-2018-5215/index.md)","id":"CVE-2018-5215","markdown":"https://insights.sbomify.com/CVE-2018-5215/index.md","name":"CVE-2018-5215","record":{"aliases":["GHSA-8fjq-cpr7-cmfp"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Fork CMS","requires_auth":"low_privilege","summary":"Cross-site scripting vulnerability in Fork CMS allows attackers to inject malicious scripts via the title parameter in the page editor.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"fork_cms","vendor":"fork-cms"}],"cvss":{"score":5.4,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Fork CMS 5.0.7 has XSS in /private/en/pages/edit via the title parameter.","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":"Fork CMS XSS Vulnerability","id":"CVE-2018-5215","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"xss","year":"2018"},"n_packages":2,"n_references":1,"next":{"headline":"Radiant CMS vulnerable to Cross-site Scripting","id":"CVE-2018-5216"},"packages":[{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["5.0.7"],"package":"forkcms/forkcms","purl":null,"source":"GHSA-8fjq-cpr7-cmfp"},{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["5.0.7"],"package":"forkcms/forkcms","purl":"pkg:composer/forkcms/forkcms","source":"GHSA-8fjq-cpr7-cmfp"}],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-5214"},"products":["n/a"],"published":"2018-01-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":"Deserialization in n/a","id":"CVE-2020-24036","kev_date_added":null,"published":"2021-03-04"},{"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":"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-09-16","vendors":["n/a"]},"summary":"Cross-site scripting vulnerability in Fork CMS allows attackers to inject malicious scripts via the title parameter in the page editor.","url":"https://insights.sbomify.com/CVE-2018-5215/"}