CVE-2019-5984

Custom CSS Pro <= 1.0.3 - Cross-site Request Forgery

2019-06-24 00:00
Dai Nakamura

Strategic Overview

Status
Patched in 1.0.4
Affected Plugin
Custom CSS Pro
Affected Version
<= 1.0.3
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2019-5984
View all Custom CSS Pro vulnerabilities

At a glance

CVE-2019-5984 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Custom CSS Pro WordPress plugin, affecting versions <= 1.0.3. 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 1.0.4; sites on affected versions should update now. Disclosed June 2019, reported by Dai Nakamura.

Vulnerability Overview

Cross-site request forgery (CSRF) vulnerability in Custom CSS Pro 1.0.3 and earlier allows remote attackers to hijack the authentication of administrators via unspecified vectors.

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 Custom CSS Pro <= 1.0.3 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 Custom CSS Pro the fix is 1.0.4: builds <= 1.0.3 are affected, anything from 1.0.4 onward is not.

Remediation

Update to version 1.0.4, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

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