CVE-2026-102772 jtsternberg CVE debrief

Who should care

Defenders responsible for WordPress sites using the CMB2 plugin, especially those with public CMB2 forms, should assess exposure and prioritize updating the plugin to a version beyond 2.13.1.

Why it matters

Defenders should prioritize verifying and updating the CMB2 plugin due to a high-severity vulnerability allowing unauthenticated Stored Cross-Site Scripting attacks on WordPress sites.

• Unauthenticated attackers can inject arbitrary web scripts in pages
• Injected scripts execute whenever a user accesses an injected page
• Exposure is trivially reachable without credentials on sites with public CMB2 forms

Technical summary

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. This is due to insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The vulnerability has a CVSS score of 7.2 and is considered HIGH severity. Defenders should prioritize verifying and updating the CMB2 plugin to a version beyond 2.13.1, and assess exposure on sites that use public CMB2 forms with textarea_code fields.

Defensive priority

Defenders should prioritize verifying and updating the CMB2 plugin to a version beyond 2.13.1, and assess exposure on sites that use public CMB2 forms with textarea_code fields.

Recommended defensive actions

• Verify and update the CMB2 plugin to a version beyond 2.13.1
• Assess exposure on sites that use public CMB2 forms with textarea_code fields
• Monitor for potential exploitation attempts
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its CVSS score of 7.2 and HIGH severity. The vulnerability is due to insufficient input sanitization and output escaping in the CMB2 plugin for WordPress.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.