# CVE-2022-1422: Discy < 5.2 - Restore Default Settings via CSRF

> An attacker can trick an admin into resetting site settings to defaults via CSRF, potentially disrupting site configuration.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-fg3m-42wq-h6wj

## What is CVE-2022-1422?

CVE-2022-1422 is a medium-severity vulnerability in Unknown Discy, published on 6 Jun 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Discy WordPress theme before 5.2 does not check for CSRF tokens in the AJAX action discy_reset_options, allowing an attacker to trick an admin into resetting the site settings back to defaults.

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

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

It affects 1 product.


Products: 2code Discy.

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

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

## Is CVE-2022-1422 being exploited?

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

## Other vulnerabilities in Unknown Discy

- [CVE-2022-1323](https://insights.sbomify.com/CVE-2022-1323/): Discy < 5.0 - Subscriber+ Broken Access Control to change settings (medium 6.5)
- [CVE-2022-1421](https://insights.sbomify.com/CVE-2022-1421/): Discy < 5.2 - Settings Update via CSRF (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-1422 is a medium-severity vulnerability in Unknown Discy, published on 6 Jun 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-1422 in the wild and no public exploit code.

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

## Sources

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

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