Skip to content
Laskyr

Path traversal and file read in WordPress plugins

Path traversal lets an attacker reach files outside the folder a plugin meant to use, usually by putting ../ in a file name. Most of these records are file reads: the attacker downloads a file they should not see.

The file attackers want most on a WordPress site is wp-config.php, which holds the database password and the secret keys. With those they may be able to log in to the database or forge login cookies.

What to do: update the plugin. If you ran a vulnerable version, change the database password and generate new salts in wp-config.php (this logs everyone out, which is the point).

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 Path traversal and file read records

336 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