{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-16870 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-16870 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-16870 is a high-severity server-side request forgery vulnerability in n/a, published on 17 Nov 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-16870 and fix it if it is affected.\n\nWhat it is: CVE-2017-16870 is a high-severity server-side request forgery vulnerability in n/a, published on 17 Nov 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-16870 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-16870/ (Markdown: https://insights.sbomify.com/CVE-2017-16870/index.md)","id":"CVE-2017-16870","markdown":"https://insights.sbomify.com/CVE-2017-16870/index.md","name":"CVE-2017-16870","record":{"aliases":["GHSA-h822-qcq8-pf95"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"An attacker can exploit Server-Side Request Forgery in the UpdraftPlus WordPress plugin to access internal resources or bypass security controls.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"updraftplus","vendor":"updraftplus"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"The UpdraftPlus plugin through 1.13.12 for WordPress has SSRF in the updraft_ajax_handler function in /wp-content/plugins/updraftplus/admin.php via an httpget subaction. NOTE: the vendor reports that this does not cross a privilege boundary","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":"Server-side request forgery in n/a","id":"CVE-2017-16870","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Race condition in n/a","id":"CVE-2017-16871"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2017-16869"},"products":["n/a"],"published":"2017-11-17","related":[{"cvss_score":8.1,"headline":"Race condition in n/a","id":"CVE-2017-16871","kev_date_added":null,"published":"2017-11-17"},{"cvss_score":7.1,"headline":"WordPress UpdraftPlus Plugin \u003c= 1.23.3 is vulnerable to Cross Site Request Forgery (CSRF)","id":"CVE-2023-32960","kev_date_added":null,"published":"2023-06-22"},{"cvss_score":6.5,"headline":"UpdraftPlus Free \u003c 1.22.3 \u0026 Premium \u003c 2.22.3 - Subscriber+ Backup Download","id":"CVE-2022-0633","kev_date_added":null,"published":"2022-02-17"},{"cvss_score":6.1,"headline":"UpdraftPlus \u003c 1.22.9 - Reflected Cross-Site Scripting","id":"CVE-2022-0864","kev_date_added":null,"published":"2022-04-04"},{"cvss_score":6.1,"headline":"UpdraftPlus \u003c 1.16.69 - Reflected Cross-Site Scripting","id":"CVE-2021-25089","kev_date_added":null,"published":"2022-02-01"},{"cvss_score":6.1,"headline":"UpdraftPlus \u003c 1.16.66 - Reflected Cross-Site Scripting","id":"CVE-2021-25022","kev_date_added":null,"published":"2022-01-03"}],"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":"An attacker can exploit Server-Side Request Forgery in the UpdraftPlus WordPress plugin to access internal resources or bypass security controls.","url":"https://insights.sbomify.com/CVE-2017-16870/"}