PatchSiren cyber security CVE debrief
CVE-2017-5612 Debian CVE debrief
CVE-2017-5612 is a cross-site scripting issue in WordPress’ admin posts list table. According to the NVD record, a crafted excerpt could inject arbitrary web script or HTML into the posts list view, and the vulnerable WordPress range extends through 4.7.1. WordPress 4.7.2 is the cited security release that addressed the issue.
- Vendor
- Debian
- Product
- Unknown
- CVSS
- MEDIUM 6.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2017-01-30
- Original CVE updated
- 2026-05-13
- Advisory published
- 2017-01-30
- Advisory updated
- 2026-05-13
Who should care
WordPress administrators and site owners running versions before 4.7.2, especially environments where users can create or edit posts and administrators routinely view the wp-admin posts list table.
Technical summary
NVD classifies this as CWE-79 with CVSS 3.0 AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N. The affected component is wp-admin/includes/class-wp-posts-list-table.php in the posts list table. The source corpus ties remediation to the WordPress 4.7.2 security release and the associated GitHub patch commit 4482f9207027de8f36630737ae085110896ea849. NVD’s vulnerable CPE criteria mark WordPress versions through 4.7.1 as affected.
Defensive priority
Medium. Patch promptly if any WordPress deployment is below 4.7.2, because the flaw can alter what is rendered in the admin interface and requires no elevated privileges in the CVSS vector.
Recommended defensive actions
- Upgrade WordPress to 4.7.2 or later.
- Confirm no production instances remain on WordPress 4.7.1 or earlier.
- Review the WordPress 4.7.2 security release notes before and after deployment.
- Use the referenced patch and advisory materials to validate that your update path includes the fix.
Evidence notes
This debrief is grounded in the supplied NVD record, which gives the CVSS vector, CWE-79 classification, affected WordPress version range through 4.7.1, and the vulnerable file path. The source corpus also includes the WordPress 4.7.2 security release notes and the specific GitHub commit referenced as the patch. The source item metadata contains Debian-related CPE criteria and Debian advisories, but the primary vulnerability description and fix references are WordPress-specific; that mapping should be treated as inventory context rather than the core issue description.
Sources and references
Verified primary and authoritative sources
-
CVE-2017-5612 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2017-5612
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2017-5612 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2017-5612
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Mitigation or vendor reference
Unverified legacy reference
URL: https://codex.wordpress.org/Version_4.7.2
[email protected] - Release Notes
-
Mitigation or vendor reference
Unverified legacy reference
URL: https://github.com/WordPress/WordPress/commit/4482f9207027de8f36630737ae085110896ea849
[email protected] - Issue Tracking, Patch
-
Mitigation or vendor reference
Unverified legacy reference
URL: https://wordpress.org/news/2017/01/wordpress-4-7-2-security-release/
[email protected] - Patch, Vendor Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.