# CVE-2026-92426: YITH WooCommerce Popup < 1.60.0 - Contributor+ Arbitrary Post Meta Deletion

> Contributors can delete arbitrary post meta from any post due to missing capability checks in the YITH WooCommerce Popup plugin.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-6j75-vpg8-hjrh

## What is CVE-2026-92426?

CVE-2026-92426 is a medium-severity missing authorization vulnerability in Unknown YITH WooCommerce Popup, published on 14 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The YITH WooCommerce Popup WordPress plugin before 1.60.0 does not check the capability of the requesting user before deleting post meta, allowing users with the Contributor role and above to delete arbitrary post meta from any post, including content owned by higher-privileged users.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-92426 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92426 is a medium-severity missing authorization vulnerability in Unknown YITH WooCommerce Popup, published on 14 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92426 in the wild and no public exploit code.

Affected product: Unknown YITH WooCommerce Popup. 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-92426/ (Markdown: https://insights.sbomify.com/CVE-2026-92426/index.md)
```

## Sources

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

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