{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-17671 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-17671 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-17671 is a critical path traversal vulnerability in Vbulletin Vbulletin, published on 14 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-17671 and fix it if it is affected.\n\nWhat it is: CVE-2017-17671 is a critical path traversal vulnerability in Vbulletin Vbulletin, published on 14 Dec 2017. 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-2017-17671 in the wild and no public exploit code.\n\nAffected product: Vbulletin Vbulletin. 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-2017-17671/ (Markdown: https://insights.sbomify.com/CVE-2017-17671/index.md)","id":"CVE-2017-17671","markdown":"https://insights.sbomify.com/CVE-2017-17671/index.md","name":"CVE-2017-17671","record":{"aliases":["GHSA-6378-4h5g-h5vx"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"vBulletin forum software","requires_auth":"none","summary":"Remote attackers can execute arbitrary PHP code on Windows vBulletin installations by exploiting directory traversal in the routestring parameter.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"vbulletin","vendor":"vbulletin"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/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":"vBulletin through 5.3.x on Windows allows remote PHP code execution because a require_once call is reachable with an unauthenticated request that can include directory traversal sequences to specify an arbitrary pathname, and because ../ traversal is blocked but ..\\ traversal is not blocked. For example, an attacker can make an invalid HTTP request containing PHP code, and then make an index.php?routestring= request with enough instances of \"..\" to reach an Apache HTTP Server log file.","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":"Path traversal in n/a","id":"CVE-2017-17671","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"vbulletin:vbulletin","products":["vbulletin:vbulletin"],"type":"path_traversal","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Deserialization in n/a","id":"CVE-2017-17672"},"packages":[],"prev":{"headline":"Use after free in n/a","id":"CVE-2017-17670"},"products":["n/a"],"published":"2017-12-14","related":[{"cvss_score":9.8,"headline":"vBulletin PHP Module Remote Code Execution","id":"CVE-2020-17496","kev_date_added":"2021-11-03","published":"2020-08-12"},{"cvss_score":9.8,"headline":"vBulletin PHP Module Remote Code Execution","id":"CVE-2019-16759","kev_date_added":"2021-11-03","published":"2019-09-24"},{"cvss_score":10,"headline":"vBulletin 5.0.0 through 5.7.5 and 6.0.0 through 6.0.3 allows unauthenticated users to invoke protected API controllers' methods when running","id":"CVE-2025-48827","kev_date_added":null,"published":"2025-05-27"},{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2023-25135","kev_date_added":null,"published":"2023-02-03"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2020-7373","kev_date_added":null,"published":"2020-10-30"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2020-12720","kev_date_added":null,"published":"2020-05-07"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2019-17132","kev_date_added":null,"published":"2019-10-04"}],"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":"Remote attackers can execute arbitrary PHP code on Windows vBulletin installations by exploiting directory traversal in the routestring parameter.","url":"https://insights.sbomify.com/CVE-2017-17671/"}