# CVE-2006-7017: File upload in n/a > Remote attackers with admin access can execute arbitrary PHP code via remote file inclusion in multiple admin scripts. - **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 15 Feb 2007 - **Updated:** 7 Aug 2024 - **Also known as:** GHSA-76v4-f74q-4qrc ## What is CVE-2006-7017? CVE-2006-7017 is a high-severity vulnerability in n/a, published on 15 Feb 2007. An attacker needs administrator access to exploit it, with no action from the victim. ### Official description Multiple PHP remote file inclusion vulnerabilities in Indexu 5.0.1 allow remote attackers to execute arbitrary PHP code via a URL in the admin_template_path parameter to admin/ scripts (1) app_change_email.php, (2) app_change_pwd.php, (3) app_mod_rewrite.php, (4) app_page_caching.php, (5) app_setup.php, (6) cat_add.php, (7) cat_delete.php, (8) cat_edit.php, (9) cat_path_update.php, (10) cat_search.php, (11) cat_struc.php, (12) cat_view.php, (13) cat_view_hidden.php, (14) cat_view_hierarchy.php, (15) cat_view_registered_only.php, (16) checkurl_web.php, (17) db_alter.php, (18) db_alter_change.php, (19) db_backup.php, (20) db_export.php, (21) db_import.php, (22) editor_add.php, (23) editor_delete.php, (24) editor_validate.php, (25) head.php, (26) index.php, (27) inv_config.php, (28) inv_config_payment.php, (29) inv_create.php, (30) inv_delete.php, (31) inv_edit.php, (32) inv_markpaid.php, (33) inv_markunpaid.php, (34) inv_overdue.php, (35) inv_paid.php, (36) inv_send.php, (37) inv_unpaid.php, (38) lang_modify.php, (39) link_add.php, (40) link_bad.php, (41) link_bad_delete.php, (42) link_checkurl.php, (43) link_delete.php, (44) link_duplicate.php, (45) link_edit.php, (46) link_premium_listing.php, (47) link_premium_sponsored.php, (48) link_search.php, (49) link_sponsored_listing.php, (50) link_validate.php, (51) link_validate_edit.php, (52) link_view.php, (53) log_search.php, (54) mail_modify.php, (55) menu.php, (56) message_create.php, (57) message_delete.php, (58) message_edit.php, (59) message_send.php, (60) message_subscriber.php, (61) message_view.php, (62) review_validate.php, (63) review_validate_edit.php, (64) summary.php, (65) template_active.php, (66) template_add_custom.php, (67) template_delete.php, (68) template_delete_file.php, (69) template_duplicate.php, (70) template_export.php, (71) template_import.php, (72) template_manager.php, (73) template_modify.php, (74) template_modify_file.php, (75) template_rename.php, (76) user_add.php, (77) user_delete.php, (78) user_edit.php, (79) user_search.php, and (80) whos.php. ## Which versions are affected by CVE-2006-7017? It affects 1 product. Products: Nicecoder Indexu. ## How do I fix CVE-2006-7017? No fix has been published for CVE-2006-7017 yet. Limit exposure of the affected software until one is available. ## Is CVE-2006-7017 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-7017 exists. Public exploit code: - Indexu 5.0.1 - 'admin_template_path' Remote File Inclusion (exploitdb) ## Other vulnerabilities in n/a - [CVE-2006-1767](https://insights.sbomify.com/CVE-2006-1767/): Code injection in n/a (high 7.5) - [CVE-2006-0688](https://insights.sbomify.com/CVE-2006-0688/): Code injection in n/a (high 7.5) - [CVE-2007-0349](https://insights.sbomify.com/CVE-2007-0349/): Path traversal in n/a (medium 5.0) - [CVE-2007-0364](https://insights.sbomify.com/CVE-2007-0364/): Cross-site scripting in n/a (medium 4.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2006-7017 and fix it if it is affected. What it is: CVE-2006-7017 is a high-severity vulnerability in n/a, published on 15 Feb 2007. An attacker needs administrator access to exploit it, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-7017 exists. Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2006-7017/ (Markdown: https://insights.sbomify.com/CVE-2006-7017/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2006-7017 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2006-7017 - OSV: https://osv.dev/vulnerability/CVE-2006-7017 --- From sbomify Insights: https://insights.sbomify.com/CVE-2006-7017/ Summaries are generated and may contain mistakes; the official description above is the record.