CVE-2019-9880

WPGraphQL <= 0.2.3 - Information Exposure

2019-05-08 00:00
Simone Quatrini

Strategic Overview

Status
Patched in 0.3.0
Affected Plugin
WPGraphQL
Affected Version
<= 0.2.3
CVSS
9.1Critical
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2019-9880
View all WPGraphQL vulnerabilities

At a glance

CVE-2019-9880 is a critical-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the WPGraphQL WordPress plugin, affecting versions <= 0.2.3. It carries a CVSS score of 9.1 (reachable over the network; low attack complexity; high confidentiality, integrity impact). Exploitation requires no authentication. The issue is fixed in version 0.3.0; sites on affected versions should update now. Disclosed May 2019, reported by Simone Quatrini.

Vulnerability Overview

An issue was discovered in WPGraphQL up to 0.2.3 . By querying the 'users' RootQuery, it is possible, for an unauthenticated attacker, to retrieve all WordPress users details such as email address, role, and username.

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.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

WPGraphQL <= 0.2.3 carries this weakness at users, and reaching it takes a caller who can reach the endpoint. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For WPGraphQL the fix is 0.3.0: builds <= 0.2.3 are affected, anything from 0.3.0 onward is not.

Remediation

Update to version 0.3.0, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: WPGraphQL 0.3.0 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

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