Radar sectionsDatabase
Check my site
WordPress plugin

CMB2 <= 2.13.1 — Unauthenticated Stored Cross-Site Scripting via 'textarea_code' Field

CVE-2026-102772Published · Updated

Action summary

Affected: ≤2.13.1Update to 2.13.2 or newer

All remediation steps
Severity
High7.2
CVSS
7.2
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:C Scope
Changed
C:L Confidentiality
Low
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-79 Cross-Site Scripting
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

CMB2 cmb2

  1. Affected≤ 2.13.1
  2. Patched in2.13.2

Update to 2.13.2 or newer.

You are affected if you run ≤ 2.13.1. Version 2.13.2 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under CMB2.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 2.13.2, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch CMB2 to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Kuba.

The CMB2 plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the '<textarea_code field id> (e.g. kl_code, kl_post_code)' parameter in all versions up to, and including, 2.13.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The front-end save path requires only a CMB2 box nonce, which is emitted to all visitors including unauthenticated guests via a simple GET request, making the attack trivially reachable without any credentials on sites that expose a public CMB2 form writing a textarea_code field.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in CMB2

All 6
More vulnerabilities in CMB2
SeverityVulnerabilityCVEPublished
Medium5.4Unauthenticated Stored Cross-Site Scripting via Grouped WYSIWYG Field via Front-End Form
≤2.13.4Update to 2.13.5
CVE-2026-116761
High7.2Unauthenticated Stored Cross-Site Scripting via 'file_list' Field Type
≤2.13.0Update to 2.13.1
CVE-2026-97336
Medium6.4Authenticated (Subscriber+) Stored Cross-Site Scripting
≤2.13.0Update to 2.13.1
CVE-2026-97270
Medium4.3Missing Authorization
≤2.12.0Update to 2.13.0
CVE-2026-80338
High7.5Authenticated (Contributor+) PHP Object Injection
≤2.10.1Update to 2.11.0
CVE-2024-1792

Same weakness (Cross-Site Scripting)

All Cross-Site Scripting
Other Cross-Site Scripting vulnerabilities
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting via Comment User-Agent HeaderCVE-2026-120688
Critical9.8Unauthenticated Arbitrary File Upload via File Upload via Public Form SubmissionCVE-2026-125055
Critical9.8Unauthenticated PHP Object Injection to Remote Code Execution via 'form' ParameterCVE-2026-119077
Medium5.3Unauthenticated Sensitive Information Exposure in 'search' Parameter
Customer Reviews for WooCommerce≤5.127.0Update to 5.128.0
CVE-2026-121518

Timeline

  1. CVE published

    Severity high, CVSS 7.2

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
CVE® identifiers
[object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?