SecuPress Free and SecuPress Pro <= 1.4.12 - Unauthenticated Arbitrary IP Ban

2021-03-22 00:00
Anonymous

Strategic Overview

Status
Patched in 2.0
Affected Version
< 2.0
CVSS
7.5High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE pending
View all SecuPress with Simple SSL – Simple and Performant Security vulnerabilities

At a glance

This record tracks a high-severity Missing Authorization vulnerability in the SecuPress with Simple SSL WordPress plugin, affecting versions < 2.0. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high availability impact). Exploitation requires no authentication. The issue is fixed in version 2.0; sites on affected versions should update now. Disclosed March 2021.

Vulnerability Overview

The SecuPress Free and SecuPress Pro plugins for WordPress is vulnerable to unauthenticated arbitrary IP bans in versions up to, and including, 1.4.12. This makes it possible for unauthenticated remote attackers to ban any IP address from accessing the site.

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. A successful exploit has high impact on availability.

CWE-862: Missing Authorization

Reaching this weakness in SecuPress with Simple SSL < 2.0 takes no account at all. 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 SecuPress with Simple SSL the fix is 2.0: builds < 2.0 are affected, anything from 2.0 onward is not.

Remediation

Update to version 2.0, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: SecuPress with Simple SSL 2.0 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