CVE-2022-4360: The WP RSS By Publishers WordPress plugin through 0.1 does not properly sanitize and escape a parameter before

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

wp rss by publishers: upgrade to newer than 0.1. Exact commands for each OS are on this page.

Q: Is CVE-2022-4360 being exploited?

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

CVE-2022-4360 affects wp rss by publishers. Severity is high (CVSS 7.2). The WP RSS By Publishers WordPress plugin through 0.1 does not properly sanitize and escape a parameter before using it in a SQL statement, leading to a SQL injection exploitable by high privilege users such as admin

Q: How urgent is CVE-2022-4360?

Priority 47/100. High severity; Public exploit reference

This month

HIGH 7.2UPGRADE

CVE-2022-4360 is a high-severity flaw (CVSS 7.2) affecting wp rss by publishers. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The WP RSS By Publishers WordPress plugin through 0.1 does not properly sanitize and escape a parameter before using it in a SQL statement, leading to a SQL injection exploitable by high privilege users such as admin

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.2 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	None
EPSS exploit chance	1.1% (top 34%)
CISA exploited list	No
Weakness	CWE-89
Published	2023-01-02
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: wp rss by publishers project

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

Am I affected?

Timeline

2023-01-02 22:15 UTCPublished CVE record published
2026-06-17 05:20 UTCUpdated Record last modified

wp rss by publishers project wp rss by publishers UPGRADE

Affected: <= 0.1

Fixed in: newer than 0.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wp-rss-by-publishers || rpm -q wp-rss-by-publishers || wp-rss-by-publishers --version

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

sudo apt update && sudo apt install --only-upgrade wp-rss-by-publishers

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wp-rss-by-publishers

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

wp rss by publishers: upgrade to newer than 0.1. Exact commands for each OS are on this page.

Is CVE-2022-4360 being exploited?

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

CVE-2022-4360 affects wp rss by publishers. Severity is high (CVSS 7.2). The WP RSS By Publishers WordPress plugin through 0.1 does not properly sanitize and escape a parameter before using it in a SQL statement, leading to a SQL injection exploitable by high privilege users such as admin

How urgent is CVE-2022-4360?

Priority 47/100. High severity; Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2022-4359 HIGH 7.2 UPGRADE The WP RSS By Publishers WordPress plugin through 0.1 does not properly sanitize and escape a parameter before
CVE-2022-4358 HIGH 7.2 UPGRADE The WP RSS By Publishers WordPress plugin through 0.1 does not properly sanitize and escape a parameter before

References

← Back to latest CVEs