CVE-2022-1758: The Genki Pre-Publish Reminder WordPress plugin through 1.4.1 does not have CSRF check in place when updating

Q: How do I fix CVE-2022-1758?

genki pre-publish reminder: upgrade to newer than 1.4.1. Exact commands for each OS are on this page.

Q: Is CVE-2022-1758 being exploited?

CVE-2022-1758 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-1758 affect?

CVE-2022-1758 affects genki pre-publish reminder. Severity is high (CVSS 8.8). 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 a

Q: How urgent is CVE-2022-1758?

Priority 48/100. High severity; Public exploit reference

This month

HIGH 8.8UPGRADE

CVE-2022-1758 is a high-severity flaw (CVSS 8.8) affecting genki pre-publish reminder. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.6% (top 51%)
CISA exploited list	No
Weakness	CWE-352
Published	2022-06-13
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: genki pre-publish reminder project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-06-13 13:15 UTCPublished CVE record published
2026-06-17 04:23 UTCUpdated Record last modified

genki pre-publish reminder project genki pre-publish reminder UPGRADE

Affected: <= 1.4.1

Fixed in: newer than 1.4.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy genki-pre-publish-reminder || rpm -q genki-pre-publish-reminder || genki-pre-publish-reminder --version

2. UPGRADE to newer than 1.4.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade genki-pre-publish-reminder

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade genki-pre-publish-reminder

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-1758?

genki pre-publish reminder: upgrade to newer than 1.4.1. Exact commands for each OS are on this page.

Is CVE-2022-1758 being exploited?

CVE-2022-1758 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-1758 affect?

CVE-2022-1758 affects genki pre-publish reminder. Severity is high (CVSS 8.8). 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 a

How urgent is CVE-2022-1758?

Priority 48/100. High severity; Public exploit reference

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs