CVE-2017-8100

CopySafe Web Protection < 2.6 - Cross-Site Request Forgery

2017-04-07 00:00
Zhiyang Zeng

Strategic Overview

Status
Patched in 2.6
Affected Version
< 2.6
CVSS
6.5Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2017-8100
View all CopySafe Web Protection – Copy Protect Images vulnerabilities

At a glance

CVE-2017-8100 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the CopySafe Web Protection WordPress plugin, affecting versions < 2.6. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 2.6; sites on affected versions should update now. Disclosed April 2017, reported by Zhiyang Zeng.

Vulnerability Overview

There is CSRF in the CopySafe Web Protection plugin before 2.6 for WordPress, allowing attackers to change plugin settings.

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 integrity.

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

Reaching this weakness in CopySafe Web Protection < 2.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 CopySafe Web Protection the fix is 2.6: builds < 2.6 are affected, anything from 2.6 onward is not.

Remediation

Update to version 2.6, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to CopySafe Web Protection: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: CopySafe Web Protection 2.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