CVE-2020-36833

Indeed Membership Pro 7.3 - 8.6 - Missing Authorization Checks

2020-02-06 00:00
Norman Riffat

Strategic Overview

Status
Patched in 8.6.1
Affected Plugin
Indeed Membership Pro
Affected Version
7.3 – 8.6
CVSS
6.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2020-36833
View all Indeed Membership Pro vulnerabilities

At a glance

CVE-2020-36833 is a medium-severity Missing Authorization vulnerability in the Indeed Membership Pro WordPress plugin, affecting versions 7.3 – 8.6. It carries a CVSS score of 6.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 8.6.1; sites on affected versions should update now. Disclosed February 2020, reported by Norman Riffat.

Vulnerability Overview

The Indeed Membership Pro plugin for WordPress is vulnerable to authorization bypass due to missing capability checks on various AJAX actions in versions 7.3 - 8.6. This makes it possible for authenticated attacker, with minimal permission, such as a subscriber, to perform a variety of actions such as modifying settings and viewing sensitive data.

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 Indeed Membership Pro 7.3 – 8.6 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 Indeed Membership Pro the fix is 8.6.1: builds 7.3 – 8.6 are affected, anything from 8.6.1 onward is not.

Remediation

Update to version 8.6.1, 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: Indeed Membership Pro 8.6.1 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