CMB2 at a glance
- 6 publicly disclosed vulnerabilities, 3 of them rated High or Critical. The most recent was disclosed on Oct 27, 2026.
- Ranked #192 by popularity on WordPress.org (300,000+ active installs).
- The latest version is 2.13.5 (released Oct 27, 2026). The most recent security fix shipped in 2.13.5.
- 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 CMB2 version
Enter the CMB2 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 “CMB2”, 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.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “CMB2”.
- 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
Update
Click “Update now” to move to the latest version (2.13.5). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known CMB2 vulnerabilities
CMB2 <= 2.13.4 - Unauthenticated Stored Cross-Site Scripting via Grouped WYSIWYG Field via Front-End Form
Cross-site scripting (XSS) · CVE-2026-116761
Affected versions: ≤ 2.13.4
Fixed in: 2.13.5
Severity: Medium 5.4 · Disclosed Oct 27, 2026
CMB2 <= 2.13.1 - Unauthenticated Stored Cross-Site Scripting via 'textarea_code' Field
Cross-site scripting (XSS) · CVE-2026-102772
Affected versions: ≤ 2.13.1
Fixed in: 2.13.2
Severity: High 7.2 · Disclosed Oct 1, 2026
CMB2 <= 2.13.0 - Unauthenticated Stored Cross-Site Scripting via 'file_list' Field Type
Cross-site scripting (XSS) · CVE-2026-97336
Affected versions: ≤ 2.13.0
Fixed in: 2.13.1
Severity: High 7.2 · Disclosed Oct 1, 2026
CMB2 <= 2.13.0 - Authenticated (Subscriber+) Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2026-97270
Affected versions: ≤ 2.13.0
Fixed in: 2.13.1
Severity: Medium 6.4 · Disclosed Sep 30, 2026
CMB2 <= 2.12.0 - Missing Authorization
Missing authorization · CVE-2026-80338
Affected versions: ≤ 2.12.0
Fixed in: 2.13.0
Severity: Medium 4.3 · Disclosed Sep 22, 2026
CMB2 <= 2.10.1 - Authenticated (Contributor+) PHP Object Injection
PHP object injection · CVE-2024-1792
Affected versions: ≤ 2.10.1
Fixed in: 2.11.0
Severity: High 7.5 · Disclosed Apr 3, 2024
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| CMB2 <= 2.13.4 - Unauthenticated Stored Cross-Site Scripting via Grouped WYSIWYG Field via Front-End FormCross-site scripting (XSS) · CVE-2026-116761 | ≤ 2.13.4 | 2.13.5 | Medium 5.4 | Oct 27, 2026 |
| CMB2 <= 2.13.1 - Unauthenticated Stored Cross-Site Scripting via 'textarea_code' FieldCross-site scripting (XSS) · CVE-2026-102772 | ≤ 2.13.1 | 2.13.2 | High 7.2 | Oct 1, 2026 |
| CMB2 <= 2.13.0 - Unauthenticated Stored Cross-Site Scripting via 'file_list' Field TypeCross-site scripting (XSS) · CVE-2026-97336 | ≤ 2.13.0 | 2.13.1 | High 7.2 | Oct 1, 2026 |
| CMB2 <= 2.13.0 - Authenticated (Subscriber+) Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2026-97270 | ≤ 2.13.0 | 2.13.1 | Medium 6.4 | Sep 30, 2026 |
| CMB2 <= 2.12.0 - Missing AuthorizationMissing authorization · CVE-2026-80338 | ≤ 2.12.0 | 2.13.0 | Medium 4.3 | Sep 22, 2026 |
| CMB2 <= 2.10.1 - Authenticated (Contributor+) PHP Object InjectionPHP object injection · CVE-2024-1792 | ≤ 2.10.1 | 2.11.0 | High 7.5 | Apr 3, 2024 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Oct 27, 2026.
Most common weaknesses in CMB2
Cross-site scripting (XSS)
4 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 CMB2 safe to use?
CMB2 is a well-known plugin with 300,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.13.5) and turn on automatic updates.
How do I find which version of CMB2 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.