# CVE-2021-24942: Menu Item Visibility Control <= 0.5 - Admin+ Arbitrary PHP Code Execution

> Highly privileged users can execute arbitrary PHP code via unsanitized menu visibility logic in the Menu Item Visibility Control plugin.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Dec 2022
- **Updated:** 14 Apr 2025
- **Also known as:** GHSA-vgw7-4fx3-67r7

## What is CVE-2021-24942?

CVE-2021-24942 is a high-severity code injection vulnerability in Unknown Menu Item Visibility Control, published on 26 Dec 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Menu Item Visibility Control WordPress plugin through 0.5 doesn't sanitize and validate the "Visibility logic" option for WordPress menu items, which could allow highly privileged users to execute arbitrary PHP code even in a hardened environment.

## Which versions are affected by CVE-2021-24942?

It affects 1 product.


Products: Menu Item Visibility Control Project Menu Item Visibility Control.

## How do I fix CVE-2021-24942?

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

## Is CVE-2021-24942 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-24942 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-24942 and fix it if it is affected.

What it is: CVE-2021-24942 is a high-severity code injection vulnerability in Unknown Menu Item Visibility Control, published on 26 Dec 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-24942 exists.

Affected product: Unknown Menu Item Visibility Control. 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-2021-24942/ (Markdown: https://insights.sbomify.com/CVE-2021-24942/index.md)
```

## Sources

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

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