# CVE-2016-20074: WordPress Lazy Content Slider Plugin 3.4 CSRF

> Attackers can trick administrators into modifying plugin settings via CSRF, requiring a patch to prevent unauthorized configuration changes.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L`)
- **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 Jun 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-6j5g-h4rw-c3j4

## What is CVE-2016-20074?

CVE-2016-20074 is a medium-severity vulnerability in leethompson Lazy Content Slider Plugin, published on 15 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

WordPress Lazy Content Slider Plugin 3.4 contains a cross-site request forgery vulnerability that allows attackers to perform unauthorized actions by crafting malicious HTML forms. Attackers can trick authenticated administrators into submitting POST requests to the plugin settings page via lzcs_admin.php to modify plugin configuration parameters like lzcs_color and lzcs_count.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2016-20074?


## How do I fix CVE-2016-20074?

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

## Is CVE-2016-20074 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-20074 and fix it if it is affected.

What it is: CVE-2016-20074 is a medium-severity vulnerability in leethompson Lazy Content Slider Plugin, published on 15 Jun 2026. 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-2016-20074 exists.

Affected product: leethompson Lazy Content Slider Plugin. 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-2016-20074/ (Markdown: https://insights.sbomify.com/CVE-2016-20074/index.md)
```

## Sources

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

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