Skip to content
Fencer Intel
medium 5.3

CVE-2019-17671 json

In WordPress before 5.2.4, unauthenticated viewing of certain content is possible because the static query property is mishandled.

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

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

Summary

In WordPress before 5.2.4, unauthenticated viewing of certain content is possible because the static query property is mishandled.

Patch / fix

  • wordpress wordpress 5.2.4
  • wordpress Debian 14, Debian 13, Debian 12 5.2.4+dfsg1-1

debian advisories DEBIAN-CVE-2019-17671

Is CVE-2019-17671 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

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-17671 updated cvss 5.3

wordpress: unauthenticated viewing of certain content is possible because the static query property is mishandled

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

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

Exploit prediction

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

Exploits and checks

  • EDB-47690 WordPress Core < 5.2.3 - Viewing Unauthenticated/Password/Private Posts webapps, 2019-10-14
  • Nuclei template WordPress <= 5.2.4 - Unauthenticated View Private/Draft Posts nuclei detection template

CVSS scores

assigned by version score vector
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
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.