{"answers":{"affected":"2 open source packages ship an affected version, including net.mingsoft:ms-mcms. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-18831 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-18831 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-18831 is a high-severity path traversal vulnerability in n/a, published on 30 Oct 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-18831 and fix it if it is affected.\n\nWhat it is: CVE-2018-18831 is a high-severity path traversal vulnerability in n/a, published on 30 Oct 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-18831 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- net.mingsoft:ms-mcms (Maven): affected all versions up to 4.6.5; no fix listed\n- net.mingsoft:ms-mcms (Maven): affected all versions up to 4.6.5; 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-18831/ (Markdown: https://insights.sbomify.com/CVE-2018-18831/index.md)","id":"CVE-2018-18831","markdown":"https://insights.sbomify.com/CVE-2018-18831/index.md","name":"CVE-2018-18831","record":{"aliases":["GHSA-7hjp-97g3-rq93"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"MCMS Java CMS","requires_auth":"none","summary":"Attackers can exploit directory traversal to write malicious JSP files to arbitrary directories, enabling remote code execution in MCMS.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mcms","vendor":"mingsoft"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"An issue was discovered in com\\mingsoft\\cms\\action\\GeneraterAction.java in MCMS 4.6.5. An attacker can write a .jsp file (in the position parameter) to an arbitrary directory via a ../ Directory Traversal in the url parameter.","ecosystems":["Maven"],"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":"Path Traversal in minsoft:ms-mcms","id":"CVE-2018-18831","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"path_traversal","year":"2018"},"n_packages":2,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2018-18832"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["4.6.5"],"package":"net.mingsoft:ms-mcms","purl":null,"source":"GHSA-7hjp-97g3-rq93"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["4.6.5"],"package":"net.mingsoft:ms-mcms","purl":"pkg:maven/net.mingsoft/ms-mcms","source":"GHSA-7hjp-97g3-rq93"}],"prev":{"headline":"Unrestricted Upload of File with Dangerous Type in mingsoft:ms-mcms","id":"CVE-2018-18830"},"products":["n/a"],"published":"2018-10-30","related":[{"cvss_score":9.8,"headline":"MCMS vulnerable SQL injection via the content_title parameter","id":"CVE-2025-56316","kev_date_added":null,"published":"2025-10-17"},{"cvss_score":9.8,"headline":"MCMS allows arbitrary file uploads in the ueditor component","id":"CVE-2025-29287","kev_date_added":null,"published":"2025-04-21"},{"cvss_score":9.8,"headline":"Mingsoft MCMS SQL injection","id":"CVE-2023-50578","kev_date_added":null,"published":"2023-12-30"},{"cvss_score":9.8,"headline":"Ming-Soft MCMS vulnerable to SQL injection","id":"CVE-2020-20913","kev_date_added":null,"published":"2023-04-04"},{"cvss_score":9.8,"headline":"Mingsoft MCMS SQL injection vulnerability in /mdiy/page/verify URI via fieldName parameter","id":"CVE-2022-36272","kev_date_added":null,"published":"2022-08-16"},{"cvss_score":9.8,"headline":"Mingsoft MCMS SQL injection vulnerability in /mdiy/model/delete URI via models List","id":"CVE-2022-36599","kev_date_added":null,"published":"2022-08-16"},{"cvss_score":9.8,"headline":"Unrestricted Upload of File with Dangerous Type in MCMS","id":"CVE-2022-31943","kev_date_added":null,"published":"2022-07-01"}],"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":"Attackers can exploit directory traversal to write malicious JSP files to arbitrary directories, enabling remote code execution in MCMS.","url":"https://insights.sbomify.com/CVE-2018-18831/"}