# CVE-2019-16251: Missing authorization in n/a

> Authenticated users can modify plugin options due to missing authorization checks in the YIT Plugin Framework for WordPress.

- **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:** 31 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rph9-hxwg-j95q

## What is CVE-2019-16251?

CVE-2019-16251 is a medium-severity missing authorization vulnerability in n/a, published on 31 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

plugin-fw/lib/yit-plugin-panel-wc.php in the YIT Plugin Framework through 3.3.8 for WordPress allows authenticated options changes.

## Which versions are affected by CVE-2019-16251?

It affects 38 products.


Products: Yithemes Yith Advanced Refund System for Woocommerce, Yithemes Yith Color and Label Variations for Woocommerce, Yithemes Yith Custom Thank You Page for Woocommerce, Yithemes Yith Desktop Notifications for Woocommerce, Yithemes Yith Paypal Express Checkout for Woocommerce, Yithemes Yith Pre-Order for Woocommerce, Yithemes Yith Product Size Charts for Woocommerce, Yithemes Yith Woocommerce Added to Cart Popup, Yithemes Yith Woocommerce Advanced Reviews, Yithemes Yith Woocommerce Affiliates, Yithemes Yith Woocommerce Ajax Search, Yithemes Yith Woocommerce Authorize.net Payment Gateway, Yithemes Yith Woocommerce Badge Management, Yithemes Yith Woocommerce Best Sellers, Yithemes Yith Woocommerce Brands Add-On, Yithemes Yith Woocommerce Bulk Product Editing, Yithemes Yith Woocommerce Cart Messages, Yithemes Yith Woocommerce Compare, Yithemes Yith Woocommerce Frequently Bought Together, Yithemes Yith Woocommerce Gift Cards and 18 more.

## How do I fix CVE-2019-16251?

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

## Is CVE-2019-16251 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-16251 and fix it if it is affected.

What it is: CVE-2019-16251 is a medium-severity missing authorization vulnerability in n/a, published on 31 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-16251 in the wild and no public exploit code.

Affected product: n/a. 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-2019-16251/ (Markdown: https://insights.sbomify.com/CVE-2019-16251/index.md)
```

## Sources

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

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