Skip to content
Laskyr

Server-side request forgery (SSRF) in WordPress plugins

Server-side request forgery makes your server fetch a URL the attacker picks. Plugins that import images, preview links or call webhooks are the usual places this shows up.

The risk is that your server can reach things the attacker cannot: services on localhost, the hosting provider’s internal network, or cloud metadata endpoints that hand out access keys. On simple shared hosting the impact is often small; on cloud servers it can be serious.

What to do: update the plugin. If you host on a cloud server, make sure the metadata service requires a token (IMDSv2 on AWS) so a forged request cannot read credentials.

Worried a plugin bug was used on your site?

The free scan reads the public side of your site and looks for spam pages, hidden redirects, injected scripts and blacklist entries. No login, no install, about a minute.

Newest Server-side request forgery (SSRF) records

269 on record for the plugins we track; the newest 100 are below. Data as of 2026-11-04.

“Affected” is the version range the source gives. “Fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. Each CVE id links to the full record on the plugin’s page.

Other types

Browse vulnerabilities

Where this data comes from

← Check a plugin · Free hacked-site scan

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit