Quasar - WordPress Theme with Animation Builder <= 1.9.2 - Authorization Bypass

2015-02-02 00:00
Evex

Strategic Overview

Status
Patched in 2.0
Affected Version
< 2.0
CVSS
8.8High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE pending
View all Quasar - WordPress Theme with Animation Builder vulnerabilities

At a glance

This record tracks a high-severity Missing Authorization vulnerability in the Quasar - WordPress Theme with Animation Builder WordPress theme, affecting versions < 2.0. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 2.0; sites on affected versions should update now. Disclosed February 2015, reported by Evex.

Vulnerability Overview

The Quasar Theme for WordPress is vulnerable to authorization bypass due to a missing capability check on the rock_builder_save_template function in versions up to, and including, 1.9.2. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to change settings and create administrator accounts.

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 Quasar - WordPress Theme with Animation Builder < 2.0 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 Quasar - WordPress Theme with Animation Builder 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?

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: Quasar - WordPress Theme with Animation Builder 2.0 closes this, and updating the theme is the step that ends it.

  • Login Security
  • Alerts

External References

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