ThinkIT WP Contact Form < 0.3 - Cross-Site Request Forgery

2013-08-15 00:00
Yashar Shahinzadeh

Strategic Overview

Status
Patched in 0.3
Affected Version
< 0.3
CVSS
4.7Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE pending
View all ThinkIT WP Contact Form vulnerabilities

At a glance

This record tracks a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the ThinkIT WP Contact Form WordPress plugin, affecting versions < 0.3. It carries a CVSS score of 4.7 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 0.3; sites on affected versions should update now. Disclosed August 2013, reported by Yashar Shahinzadeh.

Vulnerability Overview

The ThinkIT WP Contact Form plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions before 0.3. This is due to missing or incorrect nonce validation on the toitcf_create_menu_pages function. This makes it possible for unauthenticated attackers to delete forms via a 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.

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

Reaching this weakness in ThinkIT WP Contact Form < 0.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 ThinkIT WP Contact Form the fix is 0.3: builds < 0.3 are affected, anything from 0.3 onward is not.

Remediation

Update to version 0.3, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

Related records

Other vulnerabilities in ThinkIT WP Contact Form

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