# CVE-2023-6066: WP Custom Widget Area <= 1.2.5 - Subscriber+ Menus Creation/Deletion/Update

> Subscribers can create, delete, or modify site menus due to missing capability and nonce checks in AJAX callbacks.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jan 2024
- **Updated:** 9 Jan 2026
- **Also known as:** GHSA-hjg3-c5c8-mj5j

## What is CVE-2023-6066?

CVE-2023-6066 is a medium-severity missing authorization vulnerability in Unknown WP Custom Widget area, published on 15 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WP Custom Widget area WordPress plugin through 1.2.5 does not properly apply capability and nonce checks on any of its AJAX action callback functions, which could allow attackers with subscriber+ privilege to create, delete or modify menus on the site.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2023-6066?

It affects 1 product.


Products: Kishorkhambu Wp Custom Widget Area.

## How do I fix CVE-2023-6066?

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

## Is CVE-2023-6066 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-6066 and fix it if it is affected.

What it is: CVE-2023-6066 is a medium-severity missing authorization vulnerability in Unknown WP Custom Widget area, published on 15 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-6066 exists.

Affected product: Unknown WP Custom Widget area. 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-2023-6066/ (Markdown: https://insights.sbomify.com/CVE-2023-6066/index.md)
```

## Sources

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

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