CVE-2020-6167

Minimal Coming Soon & Maintenance Mode <= 2.10 - Cross-Site Request Forgery to Stored Cross-Site Scripting and Setting Changes

2020-01-08 00:00
Chloe Chamberland

Strategic Overview

Status
Patched in 2.15
Affected Version
<= 2.10
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2020-6167
View all Minimal Coming Soon – Coming Soon Page vulnerabilities

At a glance

CVE-2020-6167 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Minimal Coming Soon WordPress plugin, affecting versions <= 2.10. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.15; sites on affected versions should update now. Disclosed January 2020, reported by Chloe Chamberland.

Vulnerability Overview

A flaw in the WordPress plugin, Minimal Coming Soon & Maintenance Mode through 2.10, allows a CSRF attack to enable maintenance mode, inject XSS, modify several important settings, or include remote files as a logo.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Minimal Coming Soon <= 2.10 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Minimal Coming Soon the fix is 2.15: builds <= 2.10 are affected, anything from 2.15 onward is not.

Remediation

Update to version 2.15, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Minimal Coming Soon: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Minimal Coming Soon 2.15 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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