Skip to content
Laskyr

Plugins · revenue · data as of 2026-11-04

Is WowRevenue safe? Known vulnerabilities and latest version

WowRevenue is closed on wordpress.org

Closed on 2026-10-10. Closed plugins get no updates through WordPress, so new security holes will not be fixed for you.

Status
Closed 2026-10-10
Known issues on record
2
Unpatched in latest
0

What to do

  1. Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
  2. Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
  3. If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.

With WP-CLI, once you have a replacement: wp plugin deactivate revenue && wp plugin delete revenue

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. 2 record(s) do not state which versions are affected.

high 8.8 CVE-2026-2001 · published 2026-02-16

Remote code execution in WowRevenue (2.1.3 and older)

Affected
2.1.3 and older
Fixed in
unknown
Access needed (per CVSS)
Needs a low-level account (e.g. subscriber)
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

The WowRevenue plugin for WordPress is vulnerable to unauthorized plugin installation due to a missing capability check in the 'Notice::install_activate_plugin' function in all versions up to, and including, 2.1.3. This makes it possible for authenticated attackers, with subscriber-level access and above, to install arbitrary plugins on the affected site's server which may make remote code execution possible.

NVD CVE-2026-2001Wordfence advisoryPlugin source

medium 4.3 CVE-2025-62070 · published 2025-10-22

Missing authorization check in WowRevenue (1.2.13 and older)

Affected
1.2.13 and older
Fixed in
1.2.14
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 WPXPO WowRevenue revenue.This issue affects WowRevenue: from n/a through <= 1.2.13.

NVD CVE-2025-62070Patchstack advisory

Recent activity

Browse vulnerabilities

Where this data comes from

Badge for your site or docs (states facts with a date, not a verdict):
WowRevenue vulnerability status badge
<a href="https://laskyr.com/plugins/revenue"><img src="https://laskyr.com/plugins/revenue/badge.svg" alt="WowRevenue vulnerability status"></a>

← Check another 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