# CVE-2022-38079: WordPress Backup Scheduler plugin <= 1.5.13 - Cross-Site Request Forgery (CSRF) vulnerability

> Attackers can trick authenticated users into performing unwanted actions in the Backup Scheduler plugin, potentially altering backup settings.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A: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:** 23 Sep 2022
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-8rp5-857c-f5pv

## What is CVE-2022-38079?

CVE-2022-38079 is a medium-severity vulnerability in SedLex Backup Scheduler (WordPress plugin), published on 23 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Cross-Site Request Forgery (CSRF) vulnerability Backup Scheduler plugin <= 1.5.13 at WordPress.

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

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

It affects 1 product.


Products: Backup Scheduler Project Backup Scheduler.

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

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

## Is CVE-2022-38079 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-38079 is a medium-severity vulnerability in SedLex Backup Scheduler (WordPress plugin), published on 23 Sep 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-38079 in the wild and no public exploit code.

Affected product: SedLex Backup Scheduler (WordPress 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-2022-38079/ (Markdown: https://insights.sbomify.com/CVE-2022-38079/index.md)
```

## Sources

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

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