{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-16444 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-16444 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-16444 is a critical server-side request forgery vulnerability in Seacms Seacms, published on 4 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-16444 and fix it if it is affected.\n\nWhat it is: CVE-2018-16444 is a critical server-side request forgery vulnerability in Seacms Seacms, published on 4 Sep 2018. 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-2018-16444 in the wild and no public exploit code.\n\nAffected product: Seacms Seacms. 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-16444/ (Markdown: https://insights.sbomify.com/CVE-2018-16444/index.md)","id":"CVE-2018-16444","markdown":"https://insights.sbomify.com/CVE-2018-16444/index.md","name":"CVE-2018-16444","record":{"aliases":["GHSA-xwv8-8669-gwr6"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"SeaCMS","requires_auth":"none","summary":"An attacker can exploit a Server-Side Request Forgery vulnerability in SeaCMS to make arbitrary requests from the server.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"seacms","vendor":"seacms"}],"cvss":{"score":9.1,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"An issue was discovered in SeaCMS 6.61. adm1n/admin_reslib.php has SSRF via the url parameter.","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":"Server-side request forgery in n/a","id":"CVE-2018-16444","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"seacms:seacms","products":["seacms:seacms"],"type":"ssrf","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2018-16445"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2018-16438"},"products":["n/a"],"published":"2018-09-04","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-44073","kev_date_added":null,"published":"2025-05-06"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2025-44071","kev_date_added":null,"published":"2025-05-05"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-44072","kev_date_added":null,"published":"2025-05-05"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-44074","kev_date_added":null,"published":"2025-05-05"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-29647","kev_date_added":null,"published":"2025-04-03"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-25516","kev_date_added":null,"published":"2025-02-25"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-25517","kev_date_added":null,"published":"2025-02-25"}],"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":"2024-08-05","vendors":["n/a"]},"summary":"An attacker can exploit a Server-Side Request Forgery vulnerability in SeaCMS to make arbitrary requests from the server.","url":"https://insights.sbomify.com/CVE-2018-16444/"}