CVE-2017-5492 json
Cross-site request forgery (CSRF) vulnerability in the widget-editing accessibility-mode feature in WordPress before 4.7.1 allows remote at…
published 2017-01-15 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-14596
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.9%
- EPSS 1.9% chance of exploitation in 30 days, percentile 79%
- public exploits
- 0
- none known
Summary
Cross-site request forgery (CSRF) vulnerability in the widget-editing accessibility-mode feature in WordPress before 4.7.1 allows remote attackers to hijack the authentication of unspecified victims for requests that perform a widgets-access action, related to wp-admin/includes/class-wp-screen.php and wp-admin/widgets.php.
Patch / fix
- wordpress Debian 14, Debian 13, Debian 12 4.7.1+dfsg-1
debian advisories DEBIAN-CVE-2017-5492
- wordpress Arch Linux 4.7.1-1
arch linux advisories AVG-142
Exploit prediction
1.91% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
- Technology feeds
References
-
github.com
/WordPress/WordPress/commit/03e5c0314aeffe6b27f4b98fef842bf0fb00c733
patch
-
debian.org
/security/2017/dsa-3779
vendor-advisory
-
codex.wordpress.org
/Version_4.7.1
release-notes, vendor-advisory
-
wordpress.org
/news/2017/01/wordpress-4-7-1-security-and-maintenance-release/
vendor-advisory
- wpvulndb.com /vulnerabilities/8720
-
securityfocus.com
/bid/95407
vdb-entry
-
openwall.com
/lists/oss-security/2017/01/14/6
mailing-list, third-party-advisory
-
securitytracker.com
/id/1037591
vdb-entry
Sources
- CVE List CVE-2017-5492
- NVD CVE-2017-5492
Fencer Vulns 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.