{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-16949 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-16949 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-16949 is a critical vulnerability in n/a, published on 18 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-16949 and fix it if it is affected.\n\nWhat it is: CVE-2017-16949 is a critical vulnerability in n/a, published on 18 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-16949 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-16949/ (Markdown: https://insights.sbomify.com/CVE-2017-16949/index.md)","id":"CVE-2017-16949","markdown":"https://insights.sbomify.com/CVE-2017-16949/index.md","name":"CVE-2017-16949","record":{"aliases":["GHSA-76m2-6qg3-g4x6"],"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":"Attackers can bypass file extension restrictions to upload malicious PHP files, leading to remote code execution on the server.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"anonymous_post_pro","vendor":"accesspressthemes"}],"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-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"An issue was discovered in the AccessKeys AccessPress Anonymous Post Pro plugin through 3.1.9 for WordPress. Improper input sanitization allows the attacker to override the settings for allowed file extensions and upload file size, related to inc/cores/file-uploader.php and file-uploader/file-uploader-class.php. This allows the attacker to upload anything they want to the server, as demonstrated by an action=ap_file_upload_action\u0026allowedExtensions[]=php request to /wp-admin/admin-ajax.php that results in a .php file upload and resultant PHP code execution.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2017-12-12","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2017-12-12","kind":"exploitdb","ref":"43324","stars":null,"title":"Accesspress Anonymous Post Pro \u003c 3.2.0 - Arbitrary File Upload"}],"tier":"poc_unverified"},"has_fix":null,"headline":"File upload in n/a","id":"CVE-2017-16949","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2017-16950"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2017-16948"},"products":["n/a"],"published":"2017-12-18","related":[],"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":"Attackers can bypass file extension restrictions to upload malicious PHP files, leading to remote code execution on the server.","url":"https://insights.sbomify.com/CVE-2017-16949/"}