Is CMS Commander safe to use?

Laskyr does not give safety verdicts. CMS Commander is closed on wordpress.org. Closed on 2026-03-19 (reason given: Security Issue). Closed plugins get no updates through WordPress, so new security holes will not be fixed for you. Keep CMS Commander on the latest version and remove it if you do not use it.

Which versions of CMS Commander are vulnerable?

Known issues on record (newest first): SQL injection (2.288 and older); Privilege escalation (2.287 and older). The full list with sources is on this page.

What should I do if my CMS Commander is out of date?

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

Is CMS Commander safe? Known vulnerabilities and latest version

Status: Closed 2026-03-19
Known issues on record: 2
Unpatched in latest: 0

What to do

Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
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 cms-commander-client && wp plugin delete cms-commander-client

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-3334 · published 2026-03-21

SQL injection in CMS Commander (2.288 and older)

Affected: 2.288 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 CMS Commander plugin for WordPress is vulnerable to SQL Injection via the 'or_blogname', 'or_blogdescription', and 'or_admin_email' parameters in all versions up to, and including, 2.288. This is due to insufficient escaping on the user supplied parameters and lack of sufficient preparation on the existing SQL queries in the restore workflow. This makes it possible for authenticated attackers, with CMS Commander API key access, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

NVD CVE-2026-3334 Wordfence advisory Plugin source

critical 9.8 CVE-2023-3325 · published 2023-06-20

Privilege escalation in CMS Commander (2.287 and older)

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

Details from the advisory

The CMS Commander plugin for WordPress is vulnerable to authorization bypass due to the use of an insufficiently unique cryptographic signature on the 'cmsc_add_site' function in versions up to, and including, 2.287. This makes it possible for unauthenticated attackers to the plugin to change the '_cmsc_public_key' in the plugin config, providing access to the plugin's remote control functionalities, such as creating an admin access URL, which can be used for privilege escalation. This can only be exploited if the plugin has not been configured yet, however, if combined with another arbitrary plugin installation and activation vulnerability, the impact can be severe.

NVD CVE-2023-3325 Wordfence advisory Code change (fix)Plugin source

Recent activity

2026-03-19 — closed on wordpress.org (Security Issue).
2026-03-21 — SQL injection disclosed (CVE-2026-3334), fix version not stated.
2023-06-20 — Privilege escalation disclosed (CVE-2023-3325), fix version not stated.

Free. We check the CVE feeds every day and email you only when a new issue for CMS Commander (cms-commander-client) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: SQL injection (1) · Privilege escalation (1)

Where this data comes from

Version, last update, installs, closure: wordpress.org/plugins/cms-commander-client (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/cms-commander-client"><img src="https://laskyr.com/plugins/cms-commander-client/badge.svg" alt="CMS Commander vulnerability status"></a>

← Check another plugin · Free hacked-site scan