MiwoFTP < 1.0.6 - Cross-Site Request Forgery to Arbitrary File Deletion

2015-04-15 00:00
Gjoko Krstic

Strategic Overview

Status
Patched in 1.0.6
Affected Plugin
miwoftp
Affected Version
< 1.0.6
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE pending
View all miwoftp vulnerabilities

At a glance

This record tracks a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the miwoftp WordPress plugin, affecting versions < 1.0.6. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.0.6; sites on affected versions should update now. Disclosed April 2015, reported by Gjoko Krstic.

Vulnerability Overview

The MiwoFTP plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.0.6. This makes it possible for unauthenticated attackers to delete arbitrary files via forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in miwoftp < 1.0.6 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For miwoftp the fix is 1.0.6: builds < 1.0.6 are affected, anything from 1.0.6 onward is not.

Remediation

Update to version 1.0.6, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to miwoftp: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: miwoftp 1.0.6 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C