CVE-2018-5361

WPGlobus – Multilingual Everything! <= 1.9.6 - Cross-Site Request Forgery

2018-01-11 00:00
d4wner

Strategic Overview

Status
Patched in 1.9.7
Affected Plugin
WPGlobus
Affected Version
<= 1.9.6
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2018-5361
View all WPGlobus vulnerabilities

At a glance

CVE-2018-5361 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the WPGlobus WordPress plugin, affecting versions <= 1.9.6. 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.9.7; sites on affected versions should update now. Disclosed January 2018, reported by d4wner.

Vulnerability Overview

The WPGlobus plugin 1.9.6 for WordPress has CSRF via wp-admin/options.php.

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 WPGlobus <= 1.9.6 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 WPGlobus the fix is 1.9.7: builds <= 1.9.6 are affected, anything from 1.9.7 onward is not.

Remediation

Update to version 1.9.7, or a newer patched version

How does WordSec protect against this?

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