WordPress component: Server-side request forgery
WordPress component is affected by server-side request forgery. Exposure depends on how the affected operation is made reachable by the site. The vulnerable server can be induced to make attacker-selected network requests.
- Component
- WordPress component
- Plugin slug
- Not applicable
- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Oct 17, 2019
Update, patch or deactivate.
Update WordPress component to a release outside the affected range, or disable and remove it until a fixed version is available.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
WordPress before 5.2.4 has a Server Side Request Forgery (SSRF) vulnerability because URL validation does not consider the interpretation of a name as a series of hex characters.
NVD vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Primary and upstream sources
- NVD record for CVE-2019-17669
- Upstream reference blog.wpscan.org
- WordPress upstream reference core.trac.wordpress.org
- GitHub upstream reference github.com
- Upstream reference lists.debian.org
- Upstream reference seclists.org
- WordPress upstream reference wordpress.org
- Upstream reference wpvulndb.com
- Upstream reference debian.org
- Upstream reference debian.org
- Upstream reference blog.wpscan.org
- WordPress upstream reference core.trac.wordpress.org
- GitHub upstream reference github.com
- Upstream reference lists.debian.org
- Upstream reference seclists.org
- WordPress upstream reference wordpress.org
- Upstream reference wpvulndb.com
- Upstream reference debian.org
- Upstream reference debian.org