Skip to content
Laskyr

Sensitive data exposure in WordPress plugins

Sensitive data exposure means the plugin shows information to someone who should not see it. Examples: form submissions readable by anyone, user email addresses in a public API response, debug logs or backup files left in a public folder, or private posts visible to subscribers.

On its own this does not let anyone take over the site, but the leaked data can be personal (which may trigger privacy obligations) or useful for a later attack, such as admin usernames or API keys.

What to do: update the plugin. If the record mentions log or export files, check the plugin’s folder under wp-content/uploads for files that should not be public and delete them. If it leaked keys or passwords, change them.

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 Sensitive data exposure records

975 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