{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-46697 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-46697 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-46697 is a high-severity server-side request forgery vulnerability in stefanbohacek fediverse-embeds-wordpress-plugin, published on 11 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-46697 and fix it if it is affected.\n\nWhat it is: CVE-2026-46697 is a high-severity server-side request forgery vulnerability in stefanbohacek fediverse-embeds-wordpress-plugin, published on 11 Jun 2026. 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-2026-46697 in the wild and no public exploit code.\n\nAffected product: stefanbohacek fediverse-embeds-wordpress-plugin. 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-2026-46697/ (Markdown: https://insights.sbomify.com/CVE-2026-46697/index.md)","id":"CVE-2026-46697","markdown":"https://insights.sbomify.com/CVE-2026-46697/index.md","name":"CVE-2026-46697","record":{"aliases":["GHSA-mpq6-hjh3-m543"],"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 unauthenticated attacker can exploit an SSRF vulnerability in the Fediverse Embeds WordPress plugin to read internal resources or use the site as an open proxy.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Fediverse Embeds embeds fediverse posts on WordPress sites. Prior to version 1.5.8, Fediverse Embeds registered an unauthenticated REST route ftf/media-proxy (includes/Media_Proxy.php) with permission_callback =\u003e __return_true that accepted a base64-encoded URL and forwarded it to wp_remote_get($url) without enforcing any allowlist. The plugin's source contained a comment block explicitly acknowledging that the request should be validated against allowed fediverse domains, but in 1.5.7 the validation only set a local $can_download_media flag that was never read. The full response body was echoed back to the caller, so this was a full-read SSRF / open proxy reachable by any anonymous visitor. This issue has been patched in version 1.5.8.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Fediverse Embeds: Unauthenticated SSRF / open proxy via REST media-proxy endpoint","id":"CVE-2026-46697","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Fediverse Embeds: Public-nonce SSRF via ftf_get_site_info AJAX action","id":"CVE-2026-46698"},"packages":[],"prev":{"headline":"October CMS: Safe Mode Sandbox Bypass via Session Store and Forwarded Builder Calls","id":"CVE-2026-46696"},"products":["fediverse-embeds-wordpress-plugin"],"published":"2026-06-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-11","vendors":["stefanbohacek"]},"summary":"An unauthenticated attacker can exploit an SSRF vulnerability in the Fediverse Embeds WordPress plugin to read internal resources or use the site as an open proxy.","url":"https://insights.sbomify.com/CVE-2026-46697/"}