CVE-2019-17673
published 2019-10-17CVE-2019-17673: WordPress before 5.2.4 is vulnerable to poisoning of the cache of JSON GET requests because certain requests lack a Vary: Origin header.
PriorityP339high7.5CVSS 3.1
AVNACLPRNUINSUCNIHAN
EPSS
3.04%
86.0th percentile
WordPress before 5.2.4 is vulnerable to poisoning of the cache of JSON GET requests because certain requests lack a Vary: Origin header.
Affected
8 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| debian | debian_linux | — | — |
| debian | wordpress | < wordpress 5.2.4+dfsg1-1 (bookworm) | wordpress 5.2.4+dfsg1-1 (bookworm) |
| wordpress | wordpress | < 5.2.4 | 5.2.4 |
| wordpress | wordpress | >= 0 < 5.2.4+dfsg1-1 | 5.2.4+dfsg1-1 |
| wordpress | wordpress | >= 0 < 5.2.4+dfsg1-1 | 5.2.4+dfsg1-1 |
| wordpress | wordpress | >= 0 < 5.2.4+dfsg1-1 | 5.2.4+dfsg1-1 |
| wordpress | wordpress | >= 0 < 5.2.4+dfsg1-1 | 5.2.4+dfsg1-1 |
CVSS provenance
nvdv3.17.5HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:N/I:P/A:N
osv7.5HIGH
vendor_debian7.5HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-93gm-xcwj-q3j2: WordPress before 5
ghsa_unreviewed·2022-05-24
CVE-2019-17673 [MEDIUM] CWE-20 GHSA-93gm-xcwj-q3j2: WordPress before 5
WordPress before 5.2.4 is vulnerable to poisoning of the cache of JSON GET requests because certain requests lack a Vary: Origin header.
OSV
CVE-2019-17673: WordPress before 5
osv·2019-10-17·CVSS 7.5
CVE-2019-17673 [HIGH] CVE-2019-17673: WordPress before 5
WordPress before 5.2.4 is vulnerable to poisoning of the cache of JSON GET requests because certain requests lack a Vary: Origin header.
Debian
CVE-2019-17673: wordpress - WordPress before 5.2.4 is vulnerable to poisoning of the cache of JSON GET reque...
vendor_debian·2019·CVSS 7.5
CVE-2019-17673 [HIGH] CVE-2019-17673: wordpress - WordPress before 5.2.4 is vulnerable to poisoning of the cache of JSON GET reque...
WordPress before 5.2.4 is vulnerable to poisoning of the cache of JSON GET requests because certain requests lack a Vary: Origin header.
Scope: local
bookworm: resolved (fixed in 5.2.4+dfsg1-1)
bullseye: resolved (fixed in 5.2.4+dfsg1-1)
forky: resolved (fixed in 5.2.4+dfsg1-1)
sid: resolved (fixed in 5.2.4+dfsg1-1)
trixie: resolved (fixed in 5.2.4+dfsg1-1)
No detection rules found.
No public exploits indexed.
HackerOne
Version problem in wordpress leads to the many vulnearability
hackerone·2020-01-10·CVSS 6.1
[MEDIUM] Version problem in wordpress leads to the many vulnearability
Version problem in wordpress leads to the many vulnearability
##Title: WordPress 3.9-5.1 - Comment Cross-Site Scripting (XSS)
Reference: https://wpvulndb.com/vulnerabilities/9230
Reference: https://github.com/WordPress/WordPress/commit/0292de60ec78c5a44956765189403654fe4d080b
Reference: https://wordpress.org/news/2019/03/wordpress-5-1-1-security-and-maintenance-release/
Reference: https://blog.ripstech.com/2019/wordpress-csrf-to-rce/
Reference: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9787
## Title: WordPress <= 5.2.2 - Cross-Site Scripting (XSS) in URL Sanitisation
Reference: https://wpvulndb.com/vulnerabilities/9867
Reference: https://wordpress.org/news/2019/09/wordpress-5-2-3-security-and-maintenance-release/
Reference: https://github.com/WordPress/WordPress/commit/30a
Bugzilla
CVE-2019-17673 wordpress: JSON request cache poisoning [epel-7]
bugzilla·2019-11-22·CVSS 7.5
CVE-2019-17673 [HIGH] CVE-2019-17673 wordpress: JSON request cache poisoning [epel-7]
CVE-2019-17673 wordpress: JSON request cache poisoning [epel-7]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-7.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
Discussion:
Use the following template to for the 'fedpkg update' req
Bugzilla
CVE-2019-17673 wordpress: JSON request cache poisoning [fedora-all]
bugzilla·2019-11-22·CVSS 7.5
CVE-2019-17673 [HIGH] CVE-2019-17673 wordpress: JSON request cache poisoning [fedora-all]
CVE-2019-17673 wordpress: JSON request cache poisoning [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedora
Bugzilla
CVE-2019-17673 wordpress: JSON request cache poisoning [epel-6]
bugzilla·2019-11-22·CVSS 7.5
CVE-2019-17673 [HIGH] CVE-2019-17673 wordpress: JSON request cache poisoning [epel-6]
CVE-2019-17673 wordpress: JSON request cache poisoning [epel-6]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-6.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
Discussion:
Use the following template to for the 'fedpkg update' req
Bugzilla
CVE-2019-17673 wordpress: JSON request cache poisoning [fedora-all]
bugzilla·2019-11-21·CVSS 7.5
CVE-2019-17673 [HIGH] CVE-2019-17673 wordpress: JSON request cache poisoning [fedora-all]
CVE-2019-17673 wordpress: JSON request cache poisoning [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedora
Bugzilla
CVE-2019-17673 wordpress: JSON request cache poisoning [epel-6]
bugzilla·2019-11-21·CVSS 7.5
CVE-2019-17673 [HIGH] CVE-2019-17673 wordpress: JSON request cache poisoning [epel-6]
CVE-2019-17673 wordpress: JSON request cache poisoning [epel-6]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-6.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
Discussion:
Use the following template to for the 'fedpkg update' req
Bugzilla
CVE-2019-17673 wordpress: JSON request cache poisoning [fedora-all]
bugzilla·2019-11-20·CVSS 7.5
CVE-2019-17673 [HIGH] CVE-2019-17673 wordpress: JSON request cache poisoning [fedora-all]
CVE-2019-17673 wordpress: JSON request cache poisoning [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedora
Bugzilla
CVE-2019-17673 wordpress: JSON request cache poisoning
bugzilla·2019-11-20·CVSS 7.5
CVE-2019-17673 [HIGH] CVE-2019-17673 wordpress: JSON request cache poisoning
CVE-2019-17673 wordpress: JSON request cache poisoning
WordPress before 5.2.4 is vulnerable to poisoning of the cache of JSON GET requests because certain requests lack a Vary: Origin header.
Reference:
https://wpvulndb.com/vulnerabilities/9911
Upstream commit:
https://github.com/WordPress/WordPress/commit/b224c251adfa16a5f84074a3c0886270c9df38de
Discussion:
Created wordpress tracking bugs for this issue:
Affects: epel-6 [bug 1775739]
Affects: epel-7 [bug 1775740]
Affects: fedora-all [bug 1775738]
---
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.
https://blog.wpscan.org/wordpress/security/release/2019/10/15/wordpress-524-security-release-breakdown.htmlhttps://core.trac.wordpress.org/changeset/46478https://github.com/WordPress/WordPress/commit/b224c251adfa16a5f84074a3c0886270c9df38dehttps://seclists.org/bugtraq/2020/Jan/8https://wordpress.org/news/2019/10/wordpress-5-2-4-security-release/https://wpvulndb.com/vulnerabilities/9911https://www.debian.org/security/2020/dsa-4599https://www.debian.org/security/2020/dsa-4677https://blog.wpscan.org/wordpress/security/release/2019/10/15/wordpress-524-security-release-breakdown.htmlhttps://core.trac.wordpress.org/changeset/46478https://github.com/WordPress/WordPress/commit/b224c251adfa16a5f84074a3c0886270c9df38dehttps://seclists.org/bugtraq/2020/Jan/8https://wordpress.org/news/2019/10/wordpress-5-2-4-security-release/https://wpvulndb.com/vulnerabilities/9911https://www.debian.org/security/2020/dsa-4599https://www.debian.org/security/2020/dsa-4677
2019-10-17
Published