Is Revive.so safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (2.0.8). As of 2026-11-04. 3 issues are on record for older versions; version 2.0.8 or newer fixes all of them that state a fix. Keep Revive.so on the latest version (2.0.8) and remove it if you do not use it.

Which versions of Revive.so are vulnerable?

Known issues on record (newest first): Missing authorization check (2.0.7 and older, fixed in 2.0.8); Missing authorization check (2.0.6 and older, fixed in 2.0.7); Missing authorization check (2.0.3 and older, fixed in 2.0.4). The full list with sources is on this page.

What is the latest version of Revive.so?

2.0.8, according to wordpress.org (last updated 2026-08-14). It has 600+ active installs.

What should I do if my Revive.so is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update revive-so). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · revive-so · data as of 2026-11-04

Is Revive.so safe? Known vulnerabilities and latest version

Latest version: 2.0.8
Last updated: 2026-08-14
Active installs: 600+
Known issues on record: 3
Unpatched in latest: 0
Tested up to WP: 7.1.4 · PHP 5.6+

Revive.so is the ultimate WordPress plugin for content rejuvenation. Republish and recirculate evergreen posts with a simple click. — by WP Chill

What to do

Update to the latest version (2.0.8). Anything older than 2.0.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 revive-so --field=version shows what you run; wp plugin update revive-so 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.3 CVE-2026-39561 · published 2026-04-08

Missing authorization check in Revive.so (2.0.7 and older)

Affected: 2.0.7 and older
Fixed in: 2.0.8
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Missing Authorization vulnerability in WP Chill Revive.so revive-so allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Revive.so: from n/a through <= 2.0.7.

NVD CVE-2026-39561 Patchstack advisory

medium 4.3 CVE-2025-59551 · published 2025-09-22

Missing authorization check in Revive.so (2.0.6 and older)

Affected: 2.0.6 and older
Fixed in: 2.0.7
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Missing Authorization vulnerability in WP Chill Revive.so revive-so allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Revive.so: from n/a through <= 2.0.6.

NVD CVE-2025-59551 Patchstack advisory

medium 4.3 CVE-2025-32233 · published 2025-04-04

Missing authorization check in Revive.so (2.0.3 and older)

Affected: 2.0.3 and older
Fixed in: 2.0.4
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Missing Authorization vulnerability in WP Chill Revive.so revive-so allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Revive.so: from n/a through <= 2.0.3.

NVD CVE-2025-32233 Patchstack advisory

Recent activity

2026-08-14 — latest release on wordpress.org (2.0.8).
2026-04-08 — Missing authorization check disclosed (CVE-2026-39561), fixed in 2.0.8.
2025-09-22 — Missing authorization check disclosed (CVE-2025-59551), fixed in 2.0.7.
2025-04-04 — Missing authorization check disclosed (CVE-2025-32233), fixed in 2.0.4.

Free. We check the CVE feeds every day and email you only when a new issue for Revive.so (revive-so) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Missing authorization (3)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/revive-so (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/revive-so"><img src="https://laskyr.com/plugins/revive-so/badge.svg" alt="Revive.so vulnerability status"></a>

← Check another plugin · Free hacked-site scan

Is Revive.so safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (2.0.8)

What to do

Check your version

Known vulnerabilities

Missing authorization check in Revive.so (2.0.7 and older)

Missing authorization check in Revive.so (2.0.6 and older)

Missing authorization check in Revive.so (2.0.3 and older)

Recent activity

Get an email when Revive.so has a new vulnerability

Browse vulnerabilities

Where this data comes from