Plugins · wp-rollback · data as of 2026-11-04
Is WP Rollback safe? Known vulnerabilities and latest version
- Latest version
- 3.2.0
- Last updated
- 2026-10-08
- Active installs
- 200,000+
- Known issues on record
- 3
- Unpatched in latest
- 0
- Tested up to WP
- 7.1.4 · PHP 7.4+
Roll back (or forward) any WordPress.org plugin, theme, or block like a boss. — by Devin Walker
What to do
- Update to the latest version (3.2.0). Anything older than 3.2.0 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-rollback --field=version shows what you run; wp plugin update wp-rollback updates it.
Check your version
Known vulnerabilities
3 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 5.9 CVE-2026-66435 · published 2026-10-10
Information disclosure in WP Rollback (3.1.2 and older)
- Affected
- 3.1.2 and older
- Fixed in
- 3.2.0
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Insertion of Sensitive Information Into Sent Data vulnerability in Devin Walker WP Rollback wp-rollback allows Retrieve Embedded Sensitive Data.This issue affects WP Rollback: from n/a through 3.1.2.
medium 6.1 CVE-2015-9342 · published 2019-08-27
Cross-site scripting (XSS) in WP Rollback (older than 1.2.3)
- Affected
- older than 1.2.3
- Fixed in
- 1.2.3
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- NVD analysis · score by NVD
Details from the advisory
The wp-rollback plugin before 1.2.3 for WordPress has XSS.
high 8.8 CVE-2015-9343 · published 2019-08-27
Cross-site request forgery (CSRF) in WP Rollback (older than 1.2.3)
- Affected
- older than 1.2.3
- Fixed in
- 1.2.3
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- NVD analysis · score by NVD
Details from the advisory
The wp-rollback plugin before 1.2.3 for WordPress has CSRF.
Recent activity
- 2026-10-08 — latest release on wordpress.org (3.2.0).
- 2026-10-10 — Information disclosure disclosed (CVE-2026-66435), fixed in 3.2.0.
- 2019-08-27 — Cross-site scripting (XSS) disclosed (CVE-2015-9342), fixed in 1.2.3.
- 2019-08-27 — Cross-site request forgery (CSRF) disclosed (CVE-2015-9343), fixed in 1.2.3.
Get an email when WP Rollback has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for WP Rollback (wp-rollback) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Sensitive data exposure (1) · Cross-site scripting (XSS) (1) · Cross-site request forgery (CSRF) (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/wp-rollback (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-rollback"><img src="https://laskyr.com/plugins/wp-rollback/badge.svg" alt="WP Rollback vulnerability status"></a>