{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-11670 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-11670 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-11670 is a high-severity vulnerability in n/a, published on 1 Jun 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-11670 and fix it if it is affected.\n\nWhat it is: CVE-2018-11670 is a high-severity vulnerability in n/a, published on 1 Jun 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-11670 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-2018-11670/ (Markdown: https://insights.sbomify.com/CVE-2018-11670/index.md)","id":"CVE-2018-11670","markdown":"https://insights.sbomify.com/CVE-2018-11670/index.md","name":"CVE-2018-11670","record":{"aliases":["GHSA-vp27-2q8j-vx5m"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"GreenCMS","requires_auth":"none","summary":"Attackers can execute arbitrary PHP code via CSRF in GreenCMS admin media interface, requiring user interaction.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"greencms","vendor":"njtech"}],"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":"An issue was discovered in GreenCMS v2.3.0603. There is a CSRF vulnerability that allows attackers to execute arbitrary PHP code via the content parameter to index.php?m=admin\u0026c=media\u0026a=fileconnect.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2018-06-03","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2018-06-03","kind":"exploitdb","ref":"44825","stars":null,"title":"GreenCMS 2.3.0603 - Cross-Site Request Forgery / Remote Code Execution"}],"tier":"poc_unverified"},"has_fix":false,"headline":"Cross-site request forgery in n/a","id":"CVE-2018-11670","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2018-11671"},"packages":[],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2018-11669"},"products":["n/a"],"published":"2018-06-01","related":[{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2018-11671","kev_date_added":null,"published":"2018-06-01"},{"cvss_score":8.1,"headline":"Path traversal in n/a","id":"CVE-2022-28918","kev_date_added":null,"published":"2022-04-26"},{"cvss_score":8,"headline":"Cross-site request forgery in n/a","id":"CVE-2020-21366","kev_date_added":null,"published":"2023-06-20"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2018-12604","kev_date_added":null,"published":"2018-06-20"},{"cvss_score":7.1,"headline":"Green CMS 2.x SQL Injection via cat Parameter","id":"CVE-2019-25573","kev_date_added":null,"published":"2026-03-21"},{"cvss_score":7.1,"headline":"Green CMS 2.x Path Traversal Arbitrary File Download","id":"CVE-2019-25574","kev_date_added":null,"published":"2026-03-21"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can execute arbitrary PHP code via CSRF in GreenCMS admin media interface, requiring user interaction.","url":"https://insights.sbomify.com/CVE-2018-11670/"}