# CVE-2022-1758: Genki Pre-Publish Reminder <= 1.4.1 - Stored XSS & RCE via CSRF

> Attackers can exploit missing CSRF checks to force admins to update settings, leading to Stored XSS and Remote Code Execution.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 13 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-654h-rpxx-5fcp

## What is CVE-2022-1758?

CVE-2022-1758 is a high-severity vulnerability in Unknown Genki Pre-Publish Reminder, published on 13 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 Genki Pre-Publish Reminder WordPress plugin through 1.4.1 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack and lead to Stored XSS as well as RCE when custom code is added via the plugin settings.

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

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

It affects 1 product.


Products: Genki Pre-Publish Reminder Project Genki Pre-Publish Reminder.

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

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

## Is CVE-2022-1758 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-1758 is a high-severity vulnerability in Unknown Genki Pre-Publish Reminder, published on 13 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-1758 in the wild and no public exploit code.

Affected product: Unknown Genki Pre-Publish Reminder. 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-1758/ (Markdown: https://insights.sbomify.com/CVE-2022-1758/index.md)
```

## Sources

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

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