WP RSS Aggregator – News Feeds, Autoblogging, Youtube Video Feeds and More <= 4.6.3 - Authorization Bypass

2014-12-16 00:00
Kacper Szurek

Strategic Overview

Status
Patched in 4.6.4
Affected Plugin
WP RSS Aggregator – RSS Import, Feed to Post, Autoblogging, AI Content
Affected Version
<= 4.6.3
CVSS
6.5Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE pending
View all WP RSS Aggregator – RSS Import, Feed to Post, Autoblogging, AI Content vulnerabilities

At a glance

This record tracks a medium-severity Missing Authorization vulnerability in the WP RSS Aggregator WordPress plugin, affecting versions <= 4.6.3. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.6.4; sites on affected versions should update now. Disclosed December 2014, reported by Kacper Szurek.

Vulnerability Overview

The WP RSS Aggregator – News Feeds, Autoblogging, Youtube Video Feeds and More plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the wprss_check_if_blacklist_delete() function in versions up to, and including, 4.6.3. This makes it possible for unauthenticated attackers to delete arbitrary posts.

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 privileges on the target site, and no interaction from a victim user.

CWE-862: Missing Authorization

WP RSS Aggregator <= 4.6.3 carries this weakness at wprss_check_if_blacklist_delete(), and reaching it 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.6.4: builds <= 4.6.3 are affected, anything from 4.6.4 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/a46364f4-9258-4f5e-9d53-dcbaf726f2f0

Related records

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