CVE-2019-5924

Smart Forms < 2.6.26 - Cross-Site Request Forgery

2019-02-28 00:00
Toshiharu Sugiyama

Strategic Overview

Status
Patched in 2.6.26
Affected Version
< 2.6.26
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2019-5924
View all Smart Forms – when you need more than just a contact form vulnerabilities

At a glance

CVE-2019-5924 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Smart Forms WordPress plugin, affecting versions < 2.6.26. 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 2.6.26; sites on affected versions should update now. Disclosed February 2019, reported by Toshiharu Sugiyama.

Vulnerability Overview

Cross-site request forgery (CSRF) vulnerability in Smart Forms 2.6.15 and earlier allows remote attackers to hijack the authentication of administrators via a specially crafted page.

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 Smart Forms < 2.6.26 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 Smart Forms the fix is 2.6.26: builds < 2.6.26 are affected, anything from 2.6.26 onward is not.

Remediation

Update to version 2.6.26, or a newer patched version

How does WordSec protect against this?

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