{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-9338 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2015-9338 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-9338 is a high-severity vulnerability in n/a, published on 22 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2015-9338 and fix it if it is affected.\n\nWhat it is: CVE-2015-9338 is a high-severity vulnerability in n/a, published on 22 Aug 2019. 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-2015-9338 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-2015-9338/ (Markdown: https://insights.sbomify.com/CVE-2015-9338/index.md)","id":"CVE-2015-9338","markdown":"https://insights.sbomify.com/CVE-2015-9338/index.md","name":"CVE-2015-9338","record":{"aliases":["GHSA-f227-vq9w-7h9r"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"An attacker can upload malicious PHP files to the wp-file-upload plugin, leading to remote code execution on the WordPress site.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wordpress_file_upload","vendor":"iptanus"}],"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-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"The wp-file-upload plugin before 2.5.0 for WordPress has insufficient restrictions on upload of .php files.","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":"File upload in n/a","id":"CVE-2015-9338","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2015"},"n_packages":0,"n_references":1,"next":{"headline":"File upload in n/a","id":"CVE-2015-9339"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2015-9337"},"products":["n/a"],"published":"2019-08-22","related":[{"cvss_score":9.8,"headline":"Code injection in Iptanus File Upload","id":"CVE-2024-11613","kev_date_added":null,"published":"2025-01-08"},{"cvss_score":9.8,"headline":"WordPress File Upload \u003c= 4.24.12 - Unuathenticated Remote Code Execution","id":"CVE-2024-11635","kev_date_added":null,"published":"2025-01-08"},{"cvss_score":9.8,"headline":"The WordPress File Upload plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 4.24.11 via wfu_file_downloader.php.","id":"CVE-2024-9047","kev_date_added":null,"published":"2024-10-12"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2020-10564","kev_date_added":null,"published":"2020-03-13"},{"cvss_score":8.8,"headline":"WordPress File Upload \u003c 4.16.3 - Contributor+ Path Traversal to RCE","id":"CVE-2021-24962","kev_date_added":null,"published":"2022-03-28"},{"cvss_score":7.5,"headline":"WordPress File Upload \u003c= 4.24.13 - Unauthenticated Path Traversal to Arbitrary File Read in wfu_file_downloader.php","id":"CVE-2024-9939","kev_date_added":null,"published":"2025-01-08"}],"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-06","vendors":["n/a"]},"summary":"An attacker can upload malicious PHP files to the wp-file-upload plugin, leading to remote code execution on the WordPress site.","url":"https://insights.sbomify.com/CVE-2015-9338/"}