{"answers":{"affected":"2 open source packages ship an affected version, including wordpress and wordpress-multisite. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3590 exists.","fix":"Upgrade wordpress to a fixed version for your release line: 4.1.1 or 6.1.2.","what":"CVE-2022-3590 is a medium-severity server-side request forgery vulnerability in Wordpress Wordpress, published on 14 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-3590 and fix it if it is affected.\n\nWhat it is: CVE-2022-3590 is a medium-severity server-side request forgery vulnerability in Wordpress Wordpress, published on 14 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3590 exists.\n\nAffected packages and fixed versions:\n- wordpress (Bitnami): affected from 4.1.0; fixed in 4.1.1, 6.1.2\n- wordpress-multisite (Bitnami): affected from 4.1.0; fixed in 4.1.1, 6.1.2\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-2022-3590/ (Markdown: https://insights.sbomify.com/CVE-2022-3590/index.md)","id":"CVE-2022-3590","markdown":"https://insights.sbomify.com/CVE-2022-3590/index.md","name":"CVE-2022-3590","record":{"aliases":["BIT-wordpress-2022-3590","BIT-wordpress-multisite-2022-3590","DEBIAN-CVE-2022-3590","GHSA-mjj5-7gmf-mfjx","UBUNTU-CVE-2022-3590"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress CMS","requires_auth":"none","summary":"Unauthenticated attackers can exploit a race condition in WordPress pingbacks to perform blind SSRF and access internal network resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"wordpress","vendor":"wordpress"}],"cvss":{"score":5.9,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-367","name":"Time-of-check Time-of-use (TOCTOU) Race Condition"}],"description":"WordPress is affected by an unauthenticated blind SSRF in the pingback feature. Because of a TOCTOU race condition between the validation checks and the HTTP request, attackers can reach internal hosts that are explicitly forbidden.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":"2023-06-12","github_poc":3,"max_poc_stars":7,"metasploit":0,"nuclei":1,"refs":[{"date":"2023-06-12T13:06:54Z","kind":"github_poc","ref":"https://github.com/hxlxmj/CVE-2022-3590-WordPress-Vulnerability-Scanner","stars":7,"title":" This repository contains a Python script that checks WordPress websites for the CVE-2022-3590 vulnerability, which exploits an unauthenticated blind Server-Side Request Forgery (SSRF) in the WordPress pingback feature."},{"date":"2024-08-08T03:02:05Z","kind":"github_poc","ref":"https://github.com/huynhvanphuc/CVE-2022-3590-WordPress-Vulnerability-Scanner","stars":0,"title":null},{"date":"2026-04-22T12:03:01Z","kind":"github_poc","ref":"https://github.com/TJouleL/WordPress-6.9.1-Blind-SSRF","stars":0,"title":"Based on CVE-2022-3590, WordPress \u003c= 6.9.1 - Unauthenticated Blind SSRF via XML-RPC Pingback Discovery proof of concept (PoC)"},{"date":null,"kind":"nuclei","ref":"http/cves/2022/CVE-2022-3590.yaml","stars":null,"title":"WordPress \u003c= 6.2 - Server Side Request Forgery"}],"tier":"weaponised"},"has_fix":true,"headline":"WP \u003c= 6.1.1 - Unauthenticated Blind SSRF via DNS Rebinding","id":"CVE-2022-3590","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"wordpress:wordpress","products":["wordpress:wordpress"],"type":"ssrf","year":"2022"},"n_packages":2,"n_references":2,"next":{"headline":"Use After Free in vim/vim","id":"CVE-2022-3591"},"packages":[{"ecosystem":"Bitnami","fixed":["4.1.1","6.1.2"],"introduced":["4.1.0","4.2.0"],"last_affected":[],"package":"wordpress","purl":"pkg:bitnami/wordpress","source":"BIT-wordpress-2022-3590"},{"ecosystem":"Bitnami","fixed":["4.1.1","6.1.2"],"introduced":["4.1.0","4.2.0"],"last_affected":[],"package":"wordpress-multisite","purl":"pkg:bitnami/wordpress-multisite","source":"BIT-wordpress-multisite-2022-3590"}],"prev":{"headline":"Miele: Vulnerability in cloud service used by appWash","id":"CVE-2022-3589"},"products":["WordPress"],"published":"2022-12-14","related":[{"cvss_score":9.8,"headline":"WordPress Core Interpretation Conflict","id":"CVE-2026-63030","kev_date_added":"2026-07-21","published":"2026-07-17"},{"cvss_score":8.1,"headline":"WordPress Core Remote File Inclusion","id":"CVE-2026-87902","kev_date_added":"2026-09-25","published":"2026-09-22"},{"cvss_score":5.9,"headline":"WordPress Core SQL Injection","id":"CVE-2026-60137","kev_date_added":"2026-07-21","published":"2026-07-17"},{"cvss_score":10,"headline":"Cross-site scripting in n/a","id":"CVE-2012-2399","kev_date_added":null,"published":"2012-04-21"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2012-2400","kev_date_added":null,"published":"2012-04-21"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2011-3122","kev_date_added":null,"published":"2011-08-10"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2011-3125","kev_date_added":null,"published":"2011-08-10"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"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":"MIT","name":"Nuclei templates"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-21","vendors":["WordPress"]},"summary":"Unauthenticated attackers can exploit a race condition in WordPress pingbacks to perform blind SSRF and access internal network resources.","url":"https://insights.sbomify.com/CVE-2022-3590/"}