WordPress plugin · Updated daily · Source: Wordfence Intelligence

White Label CMS vulnerabilities: affected versions and fixes

White Label CMS has 200,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

White Label CMS at a glance

  • 8 publicly disclosed vulnerabilities, 3 of them rated High or Critical. The most recent was disclosed on Jul 10, 2026.
  • Ranked #234 by popularity on WordPress.org (200,000+ active installs).
  • The latest version is 2.7.14 (released Jul 9, 2026). The most recent security fix shipped in 2.7.13.
  • Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your White Label CMS version

Enter the White Label CMS version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “White Label CMS”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “White Label CMS”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (2.7.14). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known White Label CMS vulnerabilities

  • White Label CMS <= 2.7.12 - Authenticated (Administrator+) Stored Cross-Site Scripting via Import Settings

    Cross-site scripting (XSS) · CVE-2026-11898

    Affected versions: ≤ 2.7.12

    Fixed in: 2.7.13

    Severity: Medium 4.4 · Disclosed Jul 10, 2026

  • White Label CMS <= 2.7.4 - Reflected Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-43303

    Affected versions: ≤ 2.7.4

    Fixed in: 2.7.5

    Severity: Medium 6.1 · Disclosed Aug 16, 2024

  • White Label CMS <= 2.7.3 - Missing Authorization to Plugin Settings Reset

    Missing authorization · CVE-2024-4280

    Affected versions: ≤ 2.7.3

    Fixed in: 2.7.4

    Severity: Medium 5.3 · Disclosed May 9, 2024

  • White Label CMS <= 2.4 - Authenticated (Administrator+) PHP Object Injection

    PHP object injection · CVE-2022-4302

    Affected versions: ≤ 2.4

    Fixed in: 2.5

    Severity: High 7.2 · Disclosed Dec 8, 2022

  • White Label MS <= 2.2.8 - Reflected Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2022-0422

    Affected versions: < 2.2.9

    Fixed in: 2.2.9

    Severity: Medium 6.1 · Disclosed Feb 7, 2022

  • White Label CMS <= 1.5.2 - Cross-Site Request Forgery leading to Stored Cross-Site Scripting

    Cross-site scripting (XSS)

    Affected versions: < 1.5.3

    Fixed in: 1.5.3

    Severity: Medium 4.7 · Disclosed Apr 29, 2015

  • White Label CMS < 1.5.1 - Reflected Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2012-5387

    Affected versions: < 1.5.1

    Fixed in: 1.5.1

    Severity: High 7.1 · Disclosed Oct 21, 2012

  • White Label CMS < 1.5.1 - Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2012-5388

    Affected versions: < 1.5.1

    Fixed in: 1.5.1

    Severity: High 7.1 · Disclosed Oct 21, 2012

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Jul 10, 2026.

Most common weaknesses in White Label CMS

Cross-site scripting (XSS)

6 issues

An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.

Missing authorization

1 issue

Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.

PHP object injection

1 issue

Specially crafted data makes the server behave in unintended ways. Combined with the right conditions, it can lead to a full takeover.

Frequently asked questions

Is White Label CMS safe to use?

White Label CMS is a well-known plugin with 200,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (2.7.14) and turn on automatic updates.

How do I find which version of White Label CMS my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesWhite Label CMS on WordPress.org