Freemius SDK <= 2.2.3 - Missing Authorization to Arbitrary Options Update

2019-02-25 00:00
Anonymous

Strategic Overview

Status
Patched in 1.8.3
Affected Plugin
Popup Maker – Boost Sales, Conversions, Optins, Subscribers with the Ultimate WP Popup Builder
Affected Version
< 1.8.3
CVSS
8.8High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE pending
View all Popup Maker – Boost Sales, Conversions, Optins, Subscribers with the Ultimate WP Popup Builder vulnerabilities

At a glance

This record tracks a high-severity Missing Authorization vulnerability in the Popup Maker WordPress plugin, affecting versions < 1.8.3. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 1.8.3; sites on affected versions should update now. Disclosed February 2019.

Vulnerability Overview

The Freemius SDK for WordPress is vulnerable to authorization bypass due to a missing capability check on the _get_db_option and _set_db_option functions in versions up to, and including, 2.2.3. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to change site settings and potentially take over 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 interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-862: Missing Authorization

Reaching this weakness in Popup Maker < 1.8.3 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 Popup Maker the fix is 1.8.3: builds < 1.8.3 are affected, anything from 1.8.3 onward is not.

Remediation

Update to version 1.8.3, 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: Popup Maker 1.8.3 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/3fda31fa-efc9-44b9-99ba-9e3e23aa2ee0

Related records

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