Calculated Fields Form <= 1.0.11 - Cross-Site Request Forgery to SQL Injection

2015-03-02 00:00
Ibrahim Raafat

Strategic Overview

Status
Patched in 1.0.12
Affected Plugin
Calculated Fields Form – AI Form Builder for WordPress – Contact, Payment, Quote, Quiz & More
Affected Version
<= 1.0.11
CVSS
9.8Critical
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE pending
View all Calculated Fields Form – AI Form Builder for WordPress – Contact, Payment, Quote, Quiz & More vulnerabilities

At a glance

This record tracks a critical-severity Cross-Site Request Forgery (CSRF) vulnerability in the Calculated Fields Form WordPress plugin, affecting versions <= 1.0.11. It carries a CVSS score of 9.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.12; sites on affected versions should update now. Disclosed March 2015, reported by Ibrahim Raafat.

Vulnerability Overview

The Calculated Fields Form plugin for WordPress is vulnerable to SQL Injection via Cross-Site Request Forgery in versions up to, and including, 1.0.11 due to insufficient escaping on the user-supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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, and no interaction from a victim user. 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 Calculated Fields Form <= 1.0.11 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 Calculated Fields Form the fix is 1.0.12: builds <= 1.0.11 are affected, anything from 1.0.12 onward is not.

Remediation

Update to version 1.0.12, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/5c75c156-225c-465a-8d03-35a6669e9c04

Related records

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