{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-12895 exists.","fix":"Apply the vendor's patch.","what":"CVE-2018-12895 is a high-severity path traversal vulnerability in Debian Debian Linux, published on 26 Jun 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-12895 and fix it if it is affected.\n\nWhat it is: CVE-2018-12895 is a high-severity path traversal vulnerability in Debian Debian Linux, published on 26 Jun 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-12895 exists.\n\nAffected product: Debian Debian Linux. 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-12895/ (Markdown: https://insights.sbomify.com/CVE-2018-12895/index.md)","id":"CVE-2018-12895","markdown":"https://insights.sbomify.com/CVE-2018-12895/index.md","name":"CVE-2018-12895","record":{"aliases":["DEBIAN-CVE-2018-12895","DSA-4250-1","GHSA-v8xj-g4jr-hwhf","UBUNTU-CVE-2018-12895"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress CMS","requires_auth":"low_privilege","summary":"Authenticated Authors can delete wp-config.php via path traversal to trigger reinstallation and gain administrative privileges.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"debian_linux","vendor":"debian"},{"product":"wordpress","vendor":"wordpress"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"WordPress through 4.9.6 allows Author users to execute arbitrary code by leveraging directory traversal in the wp-admin/post.php thumb parameter, which is passed to the PHP unlink function and can delete the wp-config.php file. This is related to missing filename validation in the wp-includes/post.php wp_delete_attachment function. The attacker must have capabilities for files and posts that are normally available only to the Author, Editor, and Administrator roles. The attack methodology is to delete wp-config.php and then launch a new installation process to increase the attacker's privileges.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2018-06-26","github_poc":1,"max_poc_stars":0,"metasploit":1,"nuclei":0,"refs":[{"date":"2018-06-26","kind":"metasploit","ref":"auxiliary/scanner/http/wp_arbitrary_file_deletion","stars":null,"title":"Wordpress Arbitrary File Deletion"},{"date":"2018-07-05T19:09:17Z","kind":"github_poc","ref":"https://github.com/bloom-ux/cve-2018-12895-hotfix","stars":0,"title":"Hotfix for file deletion to to code execution vulnerability in WordPress"}],"tier":"weaponised"},"has_fix":true,"headline":"Path traversal in n/a","id":"CVE-2018-12895","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"debian:debian_linux","products":["debian:debian_linux","wordpress:wordpress"],"type":"path_traversal","year":"2018"},"n_packages":0,"n_references":6,"next":{"headline":"Integer overflow in n/a","id":"CVE-2018-12896"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2018-12893"},"products":["n/a"],"published":"2018-06-26","related":[{"cvss_score":10,"headline":"ProFTPD Improper Access Control","id":"CVE-2015-3306","kev_date_added":"2026-10-08","published":"2015-05-18"},{"cvss_score":9.9,"headline":"RoundCube Webmail Deserialization of Untrusted Data","id":"CVE-2025-49113","kev_date_added":"2026-02-20","published":"2025-06-02"},{"cvss_score":9.8,"headline":"GNU InetUtils Argument Injection","id":"CVE-2026-24061","kev_date_added":"2026-01-26","published":"2026-01-21"},{"cvss_score":9.8,"headline":"Linux Kernel Improper Check for Unusual or Exceptional Conditions","id":"CVE-2025-39682","kev_date_added":"2026-09-18","published":"2025-09-05"},{"cvss_score":9.8,"headline":"Mozilla Firefox Use-After-Free","id":"CVE-2024-9680","kev_date_added":"2024-10-15","published":"2024-10-09"},{"cvss_score":9.8,"headline":"RARLAB UnRAR Directory Traversal","id":"CVE-2022-30333","kev_date_added":"2022-08-09","published":"2022-05-09"},{"cvss_score":9.8,"headline":"Roundcube Webmail SQL Injection","id":"CVE-2021-44026","kev_date_added":"2023-06-22","published":"2021-11-19"}],"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":"BSD-3-Clause","name":"Metasploit"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Authenticated Authors can delete wp-config.php via path traversal to trigger reinstallation and gain administrative privileges.","url":"https://insights.sbomify.com/CVE-2018-12895/"}