WordPress security changelog
MEDIUM CVE-2014-9414 Modified

W3 Total Cache: Cross-site request forgery

W3 Total Cache is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.

CVE / CNA score 6.8 CVSS · cve@mitre.org
NVD score 6.8 CVSS 2.0 · nvd@nist.gov
Component
W3 Total Cache
Plugin slug
w3-total-cache
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Dec 24, 2014
Weakness
CWE-352 — Cross-Site Request Forgery (CSRF)

This CVE was published Dec 24, 2014 and is one of 19 known issues for this plugin.

What to do

Update, patch or deactivate.

Update W3 Total Cache 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.

Source record

Technical description

The W3 Total Cache plugin before 0.9.4.1 for WordPress does not properly handle empty nonces, which allows remote attackers to conduct cross-site request forgery (CSRF) attacks and hijack the authentication of administrators for requests that change the mobile site redirect URI via the mobile_groups[*][redirect] parameter and an empty _wpnonce parameter in the w3tc_mobile page to wp-admin/admin.php.

NVD vector: AV:N/AC:M/Au:N/C:P/I:P/A:P

References

Primary and upstream sources