CVE-2014-100001

SEO Plugin LiveOptim <= 1.1.3 - Cross-Site Request Forgery

2014-04-15 00:00
Anonymous

Strategic Overview

Status
Patched in 1.1.4
Affected Plugin
SEO Plugin LiveOptim
Affected Version
<= 1.1.3
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2014-100001
View all SEO Plugin LiveOptim vulnerabilities

At a glance

CVE-2014-100001 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the SEO Plugin LiveOptim WordPress plugin, affecting versions <= 1.1.3. 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.1.4; sites on affected versions should update now. Disclosed April 2014.

Vulnerability Overview

Cross-site request forgery (CSRF) vulnerability in the SEO Plugin LiveOptim plugin before 1.1.4-free for WordPress allows remote attackers to hijack the authentication of administrators for requests that change plugin settings via unspecified vectors. NOTE: some of these details are obtained from third party information.

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 SEO Plugin LiveOptim <= 1.1.3 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 SEO Plugin LiveOptim the fix is 1.1.4: builds <= 1.1.3 are affected, anything from 1.1.4 onward is not.

Remediation

Update to version 1.1.4, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

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