VulnerabilityPublished 7 Nov 2026

CVE-2026-120836: Meta Box (WordPress plugin) · Missing Authorization

Affects Meta Box (WordPress plugin)Source CVE Database V5

Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 5.15.4 when convenient.

Data as of 7 Nov 2026, 17:35 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (Patchstack)	CVSS 3.1	6.5

Patch: Available – fixed in 5.15.4

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 7 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Meta Box (WordPress plugin) to 5.15.4.

Affected software

Product	Affected	Fixed in
Meta Box – WordPress Custom Fields Frameworkmeta-box	Affected <5.15.4	Fixed in 5.15.4

AI-suggested

Upgrade to Meta Box – WordPress Custom Fields Framework version 5.15.4 or later, where this missing authorization vulnerability has been fixed.

Description

CVE-2026-120836 is a missing authorization vulnerability in the eLightUp Meta Box – WordPress Custom Fields Framework. It affects versions from the initial release up to 5.15.3. The flaw allows exploitation due to incorrectly configured access control, potentially leading to unauthorized access. A fix is available in version 5.15.4. The vulnerability has a medium severity rating with a CVSS score of 6.5.

Impact

An attacker with low privileges can exploit the missing authorization to gain unauthorized access to sensitive data, resulting in a high confidentiality impact. There is no impact on integrity or availability. No known exploits are reported in the wild.

Summary

The vulnerability CVE-2026-120836 in the Meta Box – WordPress Custom Fields Framework arises from missing authorization controls, allowing attackers with limited privileges to exploit incorrectly configured access control security levels. This affects all versions prior to 5.15.4. The vulnerability does not require user interaction and has a network attack vector. Confidentiality impact is high, while integrity and availability impacts are none. The issue was fixed in version 5.15.4.

References

patchstack.com/database/wordpress/plugin/meta-box/vulnerability/wordpress-meta-box-wordpress-custom-fields-framework-plugin-5-15-3-broken-access-control-vulnerability?_s_id=cve (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Nov 2026, 17:35 UTC

Technical details

References

Community reviews

Related threats