Plugins · wp-plugin-manager · data as of 2026-11-04
Is WP Plugin Manager safe? Known vulnerabilities and latest version
- Latest version
- 1.5.0
- Last updated
- 2026-11-03
- Active installs
- 3,000+
- Known issues on record
- 2
- Unpatched in latest
- 0
- Tested up to WP
- 7.1.4 · PHP 7.4+
WP Plugin Manager lets you disable plugins on specific pages and posts so they only load where needed. No code required. — by HasThemes
What to do
- Update to the latest version (1.5.0). Anything older than 1.4.8 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get wp-plugin-manager --field=version shows what you run; wp plugin update wp-plugin-manager updates it.
Check your version
Known vulnerabilities
2 on record, newest first. “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.
medium 6.5 CVE-2025-64271 · published 2025-11-13
Cross-site request forgery (CSRF) in WP Plugin Manager (1.4.7 and older)
- Affected
- 1.4.7 and older
- Fixed in
- 1.4.8
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
Cross-Site Request Forgery (CSRF) vulnerability in HasThemes WP Plugin Manager wp-plugin-manager allows Cross Site Request Forgery.This issue affects WP Plugin Manager: from n/a through <= 1.4.7.
medium 4.3 CVE-2023-1088 · published 2023-03-27
Cross-site request forgery (CSRF) in WP Plugin Manager (older than 1.1.8)
- Affected
- older than 1.1.8
- Fixed in
- 1.1.8
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
The WP Plugin Manager WordPress plugin before 1.1.8 does not have CSRF check when activating plugins, which could allow attackers to make logged in admins activate arbitrary plugins present on the blog via a CSRF attack
Recent activity
- 2026-11-03 — latest release on wordpress.org (1.5.0).
- 2025-11-13 — Cross-site request forgery (CSRF) disclosed (CVE-2025-64271), fixed in 1.4.8.
- 2023-03-27 — Cross-site request forgery (CSRF) disclosed (CVE-2023-1088), fixed in 1.1.8.
Get an email when WP Plugin Manager has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for WP Plugin Manager (wp-plugin-manager) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
- Published this week
- Unpatched in the latest version
- By type of vulnerability
- Plugins by HasThemes (3 tracked)
Types found in this plugin: Cross-site request forgery (CSRF) (2)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/wp-plugin-manager (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/wp-plugin-manager"><img src="https://laskyr.com/plugins/wp-plugin-manager/badge.svg" alt="WP Plugin Manager vulnerability status"></a>