Skip to content
Fencer Intel
critical 9.8

CVE-2019-9879 in the critical feed json

The WPGraphQL 0.2.3 plugin for WordPress allows remote attackers to register a new user with admin privileges, whenever new user registrati…

published 7y ago modified 4mo ago also EUVD-2019-19235

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
45.7%
EPSS 45.7% chance of exploitation in 30 days, percentile 98%
public exploits
1
Exploit-DB, plus a Nuclei check

Summary

The WPGraphQL 0.2.3 plugin for WordPress allows remote attackers to register a new user with admin privileges, whenever new user registrations are allowed. This is related to the registerUser mutation.

Patch / fix

Is CVE-2019-9879 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (EDB-46886)
  2. Published

Exploit prediction

45.69% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-46886 WordPress Plugin WPGraphQL 0.2.3 - Multiple Vulnerabilities webapps, 2019-05-21
  • Nuclei template WPGraphQL 0.2.3 - User Creation nuclei detection template
  • packetstormsecurity.com http://packetstormsecurity.com/files/153025/WordPress-WPGraphQL-0.2.3-Authentication-Bypass-Information-Disclosure.html referenced PoC, tagged "exploit" by a source, unverified
  • pentestpartners.com https://www.pentestpartners.com/security-blog/pwning-wordpress-graphql/ referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/pentestpartners/snippets/blob/master/wp-graphql0.2.3_exploit.py referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-306 Missing Authentication for Critical Functionality
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.