CVE-2024-9583

RSS Aggregator – RSS Import, News Feeds, Feed to Post, and Autoblogging <= 4.23.12 - Missing Authorization

2024-10-22 18:44
incognito

Strategic Overview

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

At a glance

CVE-2024-9583 is a medium-severity Missing Authorization vulnerability in the WP RSS Aggregator WordPress plugin, affecting versions <= 4.23.12. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 4.23.13; sites on affected versions should update now. Disclosed October 2024, reported by incognito.

Vulnerability Overview

The RSS Aggregator – RSS Import, News Feeds, Feed to Post, and Autoblogging plugin for WordPress is vulnerable to unauthorized use of functionality due to a missing capability check on the wprss_ajax_send_premium_support function in all versions up to, and including, 4.23.12. This makes it possible for authenticated attackers, with Subscriber-level access and above, to send premium support requests with an attacker-controlled subject line and email address to support allowing them to impersonate the site owner. License information may also be leaked.

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

Reaching this weakness in WP RSS Aggregator <= 4.23.12 takes a caller who can reach the endpoint. 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.13: builds <= 4.23.12 are affected, anything from 4.23.13 onward is not.

Remediation

Update to version 4.23.13, 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.13 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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