sales@hackhalt.com
Free Download

Home / Threats / CVE-2017-5489

WordPress Core - Arbitrary File Upload (CVE-2017-5489)

CVE-2017-5489

Vulnerability CVE-2017-5489 CORE wordpress HIGH

Cross-site request forgery (CSRF) vulnerability in WordPress before 4.7.1 allows remote attackers to hijack the authentication of unspecified victims via vectors involving a Flash file upload.

CVE-2017-5489

HIGH CVSS 8.8 Published 2017-01-15 Updated 2026-06-17
AI Risk High (82/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P2 Urgent
Severity Band HIGH
CVSS Vector CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Affected Components 1
Reference Links 7
AI Risk Engine High (82/100)
Exploitability High
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2017-01-15 CVE published and first recorded in the threat feed.
  2. 2026-06-17 Record updated with latest vulnerability metadata.
  3. 2026-09-18 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated just now

AI enriched just now (2026-09-18 19:20 UTC)

Technical Summary

Cross-site request forgery (CSRF) vulnerability in WordPress before 4.7.1 allows remote attackers to hijack the authentication of unspecified victims via vectors involving a Flash file upload.

Potential Impact

Severity is HIGH (CVSS 8.8). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as High based on severity and technical exposure profile.

Primary risk drivers: severity and technical exposure profile

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 82/100 (High, High) with priority P2 Urgent. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

WordPress Core CORE · wordpress Affected: <= 4.7 Fixed in: 4.7.1

Related Vulnerabilities

Browse All Threats

Newest linked vulnerabilities to keep visitors exploring adjacent CVE coverage.

WordPress Core - Security Vulnerability (CVE-2026-93485) CVE-2026-93485 Published 2026-09-18 New WordPress Core - Security Vulnerability (CVE-2026-63030) CVE-2026-63030 Published 2026-07-21 WordPress Core - SQL Injection (CVE-2026-60137) CVE-2026-60137 Published 2026-07-21 WordPress - Security Vulnerability (CVE-2026-3906) CVE-2026-3906 Published 2026-03-11 WordPress Core - Security Vulnerability (CVE-2026-25315) CVE-2026-25315 Published 2026-02-19 WordPress Core - Cross-Site Scripting (XSS) (CVE-2025-53240) CVE-2025-53240 Published 2026-01-22

References

What to do about this

Patch promptly The consequence is significant even where an attacker needs a foothold first.

Fix it

Update WordPress Core to 4.7.1 or later.

That is the complete fix. Everything below is what protects you in the meantime.

Cannot update today? Request / payload inspection (WAF) in Hack Halt ProSecure blocks this class of attack before WordPress processes the request.

Inspect request parameters and bodies for injection, traversal and file-inclusion payloads, and refuse the request rather than logging it.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs WordPress Core, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs WordPress Core. Versions below 4.7.1 are vulnerable; that release and later are not.

How do I fix it?

Update WordPress Core to version 4.7.1 or later. That is the complete fix. Until you can update, Request / payload inspection (WAF) in Hack Halt ProSecure contains this class of attack at the request layer.

What can an attacker actually do?

This is a Arbitrary File Upload flaw. An attacker who exploits it can place an executable file on the server and then run it.

WordPress security that blocks attacks before they land.

sales@hackhalt.com

Product

Resources

Company

© Hack Halt Inc. All rights reserved.