{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-1938 exists.","fix":"No fix has been published for CVE-2023-1938 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-1938 is a high-severity server-side request forgery vulnerability in Unknown WP Fastest Cache, published on 30 May 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-1938 and fix it if it is affected.\n\nWhat it is: CVE-2023-1938 is a high-severity server-side request forgery vulnerability in Unknown WP Fastest Cache, published on 30 May 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-1938 exists.\n\nAffected product: Unknown WP Fastest Cache. 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-2023-1938/ (Markdown: https://insights.sbomify.com/CVE-2023-1938/index.md)","id":"CVE-2023-1938","markdown":"https://insights.sbomify.com/CVE-2023-1938/index.md","name":"CVE-2023-1938","record":{"aliases":["GHSA-8wvj-4mr8-vx3q"],"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 a missing CSRF check and lack of input validation to perform blind server-side request forgery attacks against the WP Fastest Cache plugin.","user_interaction":"required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"wp_fastest_cache","vendor":"wpfastestcache"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"The WP Fastest Cache WordPress plugin before 1.1.5 does not have CSRF check in an AJAX action, and does not validate user input before using it in the wp_remote_get() function, leading to a Blind SSRF issue","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"WP Fatest Cache \u003c 1.1.5 - Blind SSRF via CSRF","id":"CVE-2023-1938","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"No access control for the OTP key on OTP entries","id":"CVE-2023-1939"},"packages":[],"prev":{"headline":"zhenfeng13 My-Blog userInfo cross-site request forgery","id":"CVE-2023-1937"},"products":["WP Fastest Cache"],"published":"2023-05-30","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2015-9316","kev_date_added":null,"published":"2019-08-14"},{"cvss_score":9.1,"headline":"Path traversal in n/a","id":"CVE-2019-13635","kev_date_added":null,"published":"2019-07-30"},{"cvss_score":8.8,"headline":"WP Fastest Cache \u003c 0.9.5 - Subscriber+ SQL Injection","id":"CVE-2021-24869","kev_date_added":null,"published":"2024-01-16"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2018-17584","kev_date_added":null,"published":"2019-04-15"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2015-4089","kev_date_added":null,"published":"2017-09-19"},{"cvss_score":8,"headline":"WP Fastest Cache \u003c= 0.9.0.2 - Authenticated (Subscriber+) Arbitrary File Deletion","id":"CVE-2020-36836","kev_date_added":null,"published":"2024-10-16"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-01-10","vendors":["Unknown"]},"summary":"An attacker can exploit a missing CSRF check and lack of input validation to perform blind server-side request forgery attacks against the WP Fastest Cache plugin.","url":"https://insights.sbomify.com/CVE-2023-1938/"}