CVE-2019-25217

SiteGround Optimizer <= 5.0.12 - Missing Authorization

2019-03-14 00:00
Marc-Alexandre Montpas

Strategic Overview

Status
Patched in 5.0.13
Affected Version
< 5.0.13
CVSS
9.8Critical
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2019-25217
View all Speed Optimizer – The All-In-One Performance-Boosting Plugin vulnerabilities

At a glance

CVE-2019-25217 is a critical-severity Missing Authorization vulnerability in the Speed Optimizer WordPress plugin, affecting versions < 5.0.13. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 5.0.13; sites on affected versions should update now. Disclosed March 2019, reported by Marc-Alexandre Montpas.

Vulnerability Overview

The SiteGround Optimizer plugin for WordPress is vulnerable to authorization bypass leading to Remote Code Execution and Local File Inclusion in versions up to, and including, 5.0.12 due to incorrect use of an access control attribute on the switch_php function called via the /switch-php REST API route. This allows attackers to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.

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 confidentiality, integrity, availability — full site compromise territory.

CWE-862: Missing Authorization

Speed Optimizer < 5.0.13 carries this weakness at safe, and reaching it 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 Speed Optimizer the fix is 5.0.13: builds < 5.0.13 are affected, anything from 5.0.13 onward is not.

Remediation

Update to version 5.0.13, 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: Speed Optimizer 5.0.13 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