Appsero <= 1.2.1 - Missing Authorization

2022-12-16 00:00
Anonymous

Strategic Overview

Status
Patched in 10.38
Affected Plugin
Subscribe2 – Form, Email Subscribers & Newsletters
Affected Version
<= 10.37
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE pending
View all Subscribe2 – Form, Email Subscribers & Newsletters vulnerabilities

At a glance

This record tracks a medium-severity Missing Authorization vulnerability in the Subscribe2 WordPress plugin, affecting versions <= 10.37. 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 10.38; sites on affected versions should update now. Disclosed December 2022.

Vulnerability Overview

The Appsero analytics tool used in several plugins is vulnerable to authorization bypass due to a missing capability check on the uninstall_reason_submission function used for feedback submission in versions up to, and including, 1.2.1. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to invoke this function intended for administrator use.

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 Subscribe2 <= 10.37 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 Subscribe2 the fix is 10.38: builds <= 10.37 are affected, anything from 10.38 onward is not.

Remediation

Update to version 10.38, 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: Subscribe2 10.38 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/84003388-c47c-41db-8d2d-4643aa375a89

Related records

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