{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-7402 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-7402 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-7402 is a critical vulnerability in n/a, published on 3 Apr 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-7402 and fix it if it is affected.\n\nWhat it is: CVE-2017-7402 is a critical vulnerability in n/a, published on 3 Apr 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-7402 in the wild and no public exploit code.\n\nAffected product: n/a. 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-7402/ (Markdown: https://insights.sbomify.com/CVE-2017-7402/index.md)","id":"CVE-2017-7402","markdown":"https://insights.sbomify.com/CVE-2017-7402/index.md","name":"CVE-2017-7402","record":{"aliases":["GHSA-w47h-r52j-2xjq"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Pixie CMS","requires_auth":"none","summary":"Authenticated attackers can upload and execute arbitrary PHP code by bypassing file extension checks in the Pixie CMS file manager.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pixie","vendor":"lucidcrew"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"Pixie 1.0.4 allows remote authenticated users to upload and execute arbitrary PHP code via the POST data in an admin/index.php?s=publish\u0026x=filemanager request for a filename with a double extension, such as a .jpg.php file with Content-Type of image/jpeg.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2017-04-02","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2017-04-02","kind":"exploitdb","ref":"41784","stars":null,"title":"Pixie 1.0.4 - Arbitrary File Upload"}],"tier":"poc_unverified"},"has_fix":false,"headline":"File upload in n/a","id":"CVE-2017-7402","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2017-7404"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2017-7401"},"products":["n/a"],"published":"2017-04-03","related":[{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2017-7359","kev_date_added":null,"published":"2017-03-31"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2017-7360","kev_date_added":null,"published":"2017-03-31"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2017-7361","kev_date_added":null,"published":"2017-03-31"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2017-7362","kev_date_added":null,"published":"2017-03-31"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2017-7363","kev_date_added":null,"published":"2017-03-31"},{"cvss_score":5,"headline":"Information disclosure in n/a","id":"CVE-2011-3793","kev_date_added":null,"published":"2011-09-24"}],"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":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Authenticated attackers can upload and execute arbitrary PHP code by bypassing file extension checks in the Pixie CMS file manager.","url":"https://insights.sbomify.com/CVE-2017-7402/"}