# CVE-2022-1570: Files Download Delay < 1.0.7 - Subscriber+ Settings Reset

> Authenticated subscribers can reset plugin settings due to missing authorization and CSRF checks, potentially disrupting file download delays.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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:** 6 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-fp8x-7f8g-pj5f

## What is CVE-2022-1570?

CVE-2022-1570 is a medium-severity missing authorization vulnerability in Unknown Files Download Delay, published on 6 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Files Download Delay WordPress plugin before 1.0.7 does not have authorisation and CSRF checks when reseting its settings, which could allow any authenticated users, such as subscriber to perform such action.

Weakness: CWE-862 (Missing Authorization), CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2022-1570?

It affects 1 product.


Products: Files Download Delay Project Files Download Delay.

## How do I fix CVE-2022-1570?

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

## Is CVE-2022-1570 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-1570 and fix it if it is affected.

What it is: CVE-2022-1570 is a medium-severity missing authorization vulnerability in Unknown Files Download Delay, published on 6 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-1570 in the wild and no public exploit code.

Affected product: Unknown Files Download Delay. 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-2022-1570/ (Markdown: https://insights.sbomify.com/CVE-2022-1570/index.md)
```

## Sources

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

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