CVE-2026-46698: stefanbohacek fediverse-embeds-wordpress-plugin · Server-Side Request Forgery (SSRF)
Affects stefanbohacek fediverse-embeds-wordpress-pluginSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.5.9 when convenient.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.5.9
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 11 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade stefanbohacek fediverse-embeds-wordpress-plugin to 1.5.9.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| stefanbohacekfediverse-embeds-wordpress-plugin | Affected
| Fixed in
|
AI-suggested
Upgrade the fediverse-embeds WordPress plugin to version 1.5.9 or later, where this SSRF vulnerability has been patched. No other mitigations are indicated by the vendor advisory.
Description
Fediverse Embeds embeds fediverse posts on WordPress sites. Prior to version 1.5.9, Fediverse Embeds registered the unauthenticated AJAX action wp_ajax_nopriv_ftf_get_site_info (includes/Site_Info.php) that verified a nonce ftf-fediverse-embeds-nonce and then called file_get_html($site_url) on the attacker-supplied URL. The same nonce was enqueued onto every public page containing a fediverse embed (via includes/Enqueue_Assets.php lines 41-46 + includes/Helpers.php lines 64-83), so the nonce gate was not an authentication boundary; any visitor of a public post with an embed could grab it and reuse it. This issue has been patched in version 1.5.9.