CVE-2024-6621

WP RSS Aggregator <= 4.23.11 - Missing Authorization to Authenticated (Subscriber+) Feed State Update

2024-07-15 00:00
Peter Thaleikis

Strategic Overview

Status
Patched in 4.23.12
Affected Plugin
WP RSS Aggregator – RSS Import, Feed to Post, Autoblogging, AI Content
Affected Version
<= 4.23.11
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-6621
View all WP RSS Aggregator – RSS Import, Feed to Post, Autoblogging, AI Content vulnerabilities

At a glance

CVE-2024-6621 is a medium-severity Missing Authorization vulnerability in the WP RSS Aggregator WordPress plugin, affecting versions <= 4.23.11. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 4.23.12; sites on affected versions should update now. Disclosed July 2024, reported by Peter Thaleikis.

Vulnerability Overview

The RSS Aggregator – RSS Import, News Feeds, Feed to Post, and Autoblogging plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'wprss_activate_feed_source' and 'wprss_pause_feed_source' functions in all versions up to, and including, 4.23.11. This makes it possible for authenticated attackers, with Subscriber-level access and above, to activate or pause existing RSS feeds.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-862: Missing Authorization

WP RSS Aggregator <= 4.23.11 carries this weakness at wprss_activate_feed_source, and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WP RSS Aggregator the fix is 4.23.12: builds <= 4.23.11 are affected, anything from 4.23.12 onward is not.

Remediation

Update to version 4.23.12, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WP RSS Aggregator 4.23.12 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-6621https://www.wordfence.com/threat-intel/vulnerabilities/id/8e37331b-0b75-41ee-b390-532efd674cc1https://nvd.nist.gov/vuln/detail/CVE-2024-6621

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C