CVE-2026-120836: Meta Box WordPress Custom Fields Framework broken access control

CVE-2026-120836 · Severity: medium · CVSS 6.5 · Published 2026-11-07

Meta Box is a WordPress plugin that enables custom fields and data management for website administrators. A broken access control vulnerability allows users with the Contributor role to access or perform actions they should not be authorized to do, potentially exposing sensitive data or enabling unauthorized modifications. An attacker with low privileges could exploit misconfigured access control to view or manipulate protected content.

Technologies: eLightUp Meta Box – WordPress Custom Fields Framework. Vendors: eLightUp.

Quick answers

Is CVE-2026-120836 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-120836 being exploited in the wild.
How severe is CVE-2026-120836?
Medium severity, with a CVSS score of 6.5, published 7 November 2026.
Which products and versions are affected?
eLightUp Meta Box – WordPress Custom Fields Framework 5.15.3 and earlier.
Is there a fix for CVE-2026-120836?
Yes: fixed in 5.15.4. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-120836 attacked?
It is attacked over the network.
Am I affected by CVE-2026-120836?
Check whether you run eLightUp Meta Box – WordPress Custom Fields Framework at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: 5.15.4

Technical details

A broken access control vulnerability in Meta Box allows privilege escalation where Contributor-level users can bypass authorization checks. The vulnerability stems from incorrectly configured access control security levels in the plugin, allowing authenticated users to perform restricted operations. No public exploit is known.

Affected products

  • eLightUp Meta Box – WordPress Custom Fields Framework 5.15.3 and earlier

Timeline

  • 2026-10-25: disclosed
  • 2026-11-07: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.