CVE-2022-1779: The Auto Delete Posts WordPress plugin through 1.3.0 does not have CSRF check in place when updating its setti

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

auto delete posts: upgrade to newer than 1.3.0. Exact commands for each OS are on this page.

Q: Is CVE-2022-1779 being exploited?

CVE-2022-1779 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-1779 affect?

CVE-2022-1779 affects auto delete posts. Severity is high (CVSS 8.1). The Auto Delete Posts WordPress plugin through 1.3.0 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 delete specific posts, categories and

Q: How urgent is CVE-2022-1779?

Priority 44/100. High severity; Public exploit reference

This month

HIGH 8.1UPGRADE

CVE-2022-1779 is a high-severity flaw (CVSS 8.1) affecting auto delete posts. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Auto Delete Posts WordPress plugin through 1.3.0 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 delete specific posts, categories and attachments at once.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

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

Publisher (CNA): WPScan · Vendor: auto delete posts 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

auto delete posts project auto delete posts UPGRADE

Affected: <= 1.3.0

Fixed in: newer than 1.3.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy auto-delete-posts || rpm -q auto-delete-posts || auto-delete-posts --version

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

sudo apt update && sudo apt install --only-upgrade auto-delete-posts

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade auto-delete-posts

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-1779?

auto delete posts: upgrade to newer than 1.3.0. Exact commands for each OS are on this page.

Is CVE-2022-1779 being exploited?

CVE-2022-1779 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-1779 affect?

CVE-2022-1779 affects auto delete posts. Severity is high (CVSS 8.1). The Auto Delete Posts WordPress plugin through 1.3.0 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 delete specific posts, categories and

How urgent is CVE-2022-1779?

Priority 44/100. High severity; Public exploit reference

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs