{"answers":{"affected":"2 open source packages ship an affected version, including yoast-seo-for-typo3/yoast_seo. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-31779 in the wild and no public exploit code.","fix":"Upgrade yoast-seo-for-typo3/yoast_seo to 7.2.1 or later.","what":"CVE-2021-31779 is a medium-severity server-side request forgery vulnerability in n/a, published on 28 Apr 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-31779 and fix it if it is affected.\n\nWhat it is: CVE-2021-31779 is a medium-severity server-side request forgery vulnerability in n/a, published on 28 Apr 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-31779 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- yoast-seo-for-typo3/yoast_seo (Packagist): affected all versions; fixed in 7.2.1\n- yoast-seo-for-typo3/yoast_seo (Packagist): affected all versions; fixed in 7.2.1\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-2021-31779/ (Markdown: https://insights.sbomify.com/CVE-2021-31779/index.md)","id":"CVE-2021-31779","markdown":"https://insights.sbomify.com/CVE-2021-31779/index.md","name":"CVE-2021-31779","record":{"aliases":["GHSA-m2q4-qghh-p9cq"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"TYPO3 SEO plugin","requires_auth":"low_privilege","summary":"An attacker with a backend account can exploit Server-Side Request Forgery in the Yoast SEO extension to access internal resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"yoast_seo","vendor":"yoast"}],"cvss":{"score":6.4,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"The yoast_seo (aka Yoast SEO) extension before 7.2.1 for TYPO3 allows SSRF via a backend user account.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Server-Side Request Forgery in yoast_seo","id":"CVE-2021-31779","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"ssrf","year":"2021"},"n_packages":2,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2021-31780"},"packages":[{"ecosystem":"Packagist","fixed":["7.2.1"],"introduced":["0"],"last_affected":[],"package":"yoast-seo-for-typo3/yoast_seo","purl":null,"source":"GHSA-m2q4-qghh-p9cq"},{"ecosystem":"Packagist","fixed":["7.2.1"],"introduced":["0"],"last_affected":[],"package":"yoast-seo-for-typo3/yoast_seo","purl":"pkg:composer/yoast-seo-for-typo3/yoast_seo","source":"GHSA-m2q4-qghh-p9cq"}],"prev":{"headline":"Cross-site scripting in media2click","id":"CVE-2021-31778"},"products":["n/a"],"published":"2021-04-28","related":[{"cvss_score":9.9,"headline":"Cross-site scripting in n/a","id":"CVE-2019-13478","kev_date_added":null,"published":"2019-07-09"},{"cvss_score":7.1,"headline":"WordPress Yoast SEO: Local Plugin \u003c= 14.8 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-32300","kev_date_added":null,"published":"2023-08-23"},{"cvss_score":6.6,"headline":"Race condition in n/a","id":"CVE-2018-19370","kev_date_added":null,"published":"2018-11-28"},{"cvss_score":6.5,"headline":"WordPress Yoast SEO: Local Plugin \u003c= 14.9 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-28785","kev_date_added":null,"published":"2023-05-28"},{"cvss_score":5.9,"headline":"WordPress Yoast SEO Plugin \u003c= 21.0 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-40680","kev_date_added":null,"published":"2023-11-30"},{"cvss_score":5.4,"headline":"Cross-site Scripting in the yoast_seo TYPO3 extension","id":"CVE-2021-36788","kev_date_added":null,"published":"2021-08-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-03","vendors":["n/a"]},"summary":"An attacker with a backend account can exploit Server-Side Request Forgery in the Yoast SEO extension to access internal resources.","url":"https://insights.sbomify.com/CVE-2021-31779/"}