# CVE-2026-109700: WordPress Meta Box – WordPress Custom Fields Framework plugin <= 5.15.2 - Broken Access Control vulnerability


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-cpcj-mprm-rqgp

## What is CVE-2026-109700?

CVE-2026-109700 is a medium-severity vulnerability in eLightUp Meta Box – WordPress Custom Fields Framework, published on 20 Oct 2026. 

### Official description

Missing Authorization vulnerability in eLightUp Meta Box – WordPress Custom Fields Framework meta-box allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Meta Box – WordPress Custom Fields Framework: from n/a through 5.15.2.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-109700?


## How do I fix CVE-2026-109700?

No fix has been published for CVE-2026-109700 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-109700 being exploited?

There is no known exploitation of CVE-2026-109700 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-109700 and fix it if it is affected.

What it is: CVE-2026-109700 is a medium-severity vulnerability in eLightUp Meta Box – WordPress Custom Fields Framework, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-109700 in the wild and no public exploit code.

Affected product: eLightUp Meta Box – WordPress Custom Fields Framework. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-109700/ (Markdown: https://insights.sbomify.com/CVE-2026-109700/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-109700
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-109700
- OSV: https://osv.dev/vulnerability/CVE-2026-109700

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-109700/
Summaries are generated and may contain mistakes; the official description above is the record.