Is ManageWP Worker safe to use?

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

Which versions of ManageWP Worker are vulnerable?

Known issues on record (newest first): Authentication bypass (older than 4.9.37, fixed in 4.9.37); Cross-site scripting (XSS) (4.9.31 and older, fixed in 4.9.32); Stored cross-site scripting (XSS) (4.9.31 and older, fixed in 4.9.32). The full list with sources is on this page.

What is the latest version of ManageWP Worker?

4.9.38, according to wordpress.org (last updated 2026-08-21). It has 1+ million active installs.

What should I do if my ManageWP Worker is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update worker). 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 · worker · data as of 2026-11-01

Is ManageWP Worker safe? Known vulnerabilities and latest version

Latest version: 4.9.38
Last updated: 2026-08-21
Active installs: 1+ million
Known issues on record: 3
Unpatched in latest: 0
Tested up to WP: 7.1.4

A better way to manage dozens of WordPress websites. — by ManageWP

What to do

Update to the latest version (4.9.38). Anything older than 4.9.37 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 worker --field=version shows what you run; wp plugin update worker 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.

high 8.1 CVE-2026-18052 · published 2026-08-22

Authentication bypass in ManageWP Worker (older than 4.9.37)

Affected: older than 4.9.37
Fixed in: 4.9.37
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by CISA ADP

Details from the advisory

The ManageWP Worker WordPress plugin before 4.9.37 does not bind the account being logged in to the signature which authorises the login, nor prevent an already used login link from being replayed, allowing attackers who obtain such a link to gain a session as any user on the site, including an administrator.

NVD CVE-2026-18052 WPScan advisory

high 7.1 CVE-2026-39463 · published 2026-06-15

Cross-site scripting (XSS) in ManageWP Worker (4.9.31 and older)

Affected: 4.9.31 and older
Fixed in: 4.9.32
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 Patchstack

Details from the advisory

Unauthenticated Cross Site Scripting (XSS) in ManageWP Worker <= 4.9.31 versions.

NVD CVE-2026-39463 Patchstack advisory

high 7.2 CVE-2026-3718 · published 2026-05-14

Stored cross-site scripting (XSS) in ManageWP Worker (4.9.31 and older)

Affected: 4.9.31 and older
Fixed in: 4.9.32 *
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The ManageWP Worker plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'MWP-Key-Name' HTTP request header in all versions up to, and including, 4.9.31. This is due to insufficient input sanitization and output escaping of attacker-controlled header values. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever an administrator visits the plugin's connection management page with debug parameters.

NVD CVE-2026-3718 Wordfence advisory Code change (fix)

Recent activity

2026-08-21 — latest release on wordpress.org (4.9.38).
2026-08-22 — Authentication bypass disclosed (CVE-2026-18052), fixed in 4.9.37.
2026-06-15 — Cross-site scripting (XSS) disclosed (CVE-2026-39463), fixed in 4.9.32.
2026-05-14 — Stored cross-site scripting (XSS) disclosed (CVE-2026-3718), fixed in 4.9.32.

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

Where this data comes from

Version, last update, installs: wordpress.org/plugins/worker (Plugins API), fetched 2026-11-01.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-01. 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/worker"><img src="https://laskyr.com/plugins/worker/badge.svg" alt="ManageWP Worker vulnerability status"></a>

← Check another plugin · Free hacked-site scan

Is ManageWP Worker safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (4.9.38)

What to do

Check your version

Known vulnerabilities

Authentication bypass in ManageWP Worker (older than 4.9.37)

Cross-site scripting (XSS) in ManageWP Worker (4.9.31 and older)

Stored cross-site scripting (XSS) in ManageWP Worker (4.9.31 and older)

Recent activity

Get an email when ManageWP Worker has a new vulnerability

Where this data comes from