Skip to main content
VulnerabilityPublished

CVE-2026-80338: CMB2 (WordPress plugin) · Missing Authorization

Affects CMB2 (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.8 Medium : upgrade to 2.13.0 when convenient.

Data as of 7 Nov 2026, 23:24 UTC

CVSS 3.1 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.13.0
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

What to do

Upgrade CMB2 (WordPress plugin) to 2.13.0.

Affected software

ProductAffectedFixed in
CMB2Affected
  • <2.13.0
Fixed in
  • 2.13.0

AI-suggested

Upgrade the CMB2 WordPress plugin to version 2.13.0 or later, where this authorization issue is fixed. No other mitigation is indicated. Patch status is not explicitly confirmed in the input data, so verify with the vendor advisory for current remediation guidance.

Description

The CMB2 WordPress plugin before 2.13.0 does not perform any capability check on one of its AJAX actions, allowing users with a role as low as Subscriber to create arbitrary WordPress options and corrupt existing ones, which can break core site settings and take the site offline. Exploitation requires the site's or another CMB2 WordPress plugin before 2.13.0 to have declared an oEmbed field, as the CMB2 WordPress plugin before 2.13.0 registers none of its own. The stored value is never attacker-controlled, so the issue does not lead to privilege escalation.

References

Community reviews

Loading reviews…