# CVE-2019-15650: Cross-site request forgery in n/a

> Attackers can bypass security controls to disable unattended theme updates due to a missing nonce check in the stops-core-theme-and-plugin-updates plugin.

- **Severity:** Medium 4.3 (`CVSS:3.0/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:** 27 Aug 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mrg7-x5vh-pv4c

## What is CVE-2019-15650?

CVE-2019-15650 is a medium-severity vulnerability in n/a, published on 27 Aug 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The stops-core-theme-and-plugin-updates plugin before 8.0.5 for WordPress has insufficient restrictions on option changes (such as disabling unattended theme updates) because of a nonce check error.

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

It affects 1 product.


Products: Easyupdatesmanager Easy Updates Manager.

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

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

## Is CVE-2019-15650 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-15650 is a medium-severity vulnerability in n/a, published on 27 Aug 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-15650 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-15650/ (Markdown: https://insights.sbomify.com/CVE-2019-15650/index.md)
```

## Sources

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

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