CVE-2019-17237

IgniteUp – Coming Soon and Maintenance Mode <= 3.4.0 - Cross-Site Request Forgery

2019-11-10 00:00
Anonymous

Strategic Overview

Status
Patched in 3.4.1
Affected Version
<= 3.4.0
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2019-17237
View all IgniteUp – Coming Soon and Maintenance Mode vulnerabilities

At a glance

CVE-2019-17237 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the IgniteUp WordPress plugin, affecting versions <= 3.4.0. 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 3.4.1; sites on affected versions should update now. Disclosed November 2019.

Vulnerability Overview

includes/class-coming-soon-creator.php in the igniteup plugin through 3.4 for WordPress allows CSRF.

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 IgniteUp <= 3.4.0 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 IgniteUp the fix is 3.4.1: builds <= 3.4.0 are affected, anything from 3.4.1 onward is not.

Remediation

Update to version 3.4.1, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to IgniteUp: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: IgniteUp 3.4.1 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