CVE-2015-1874

Contact Form DB <= 2.8.29 - Cross-site request forgery via a request in the CF7DBPluginSubmissions page to wp-admin/admin.php

2015-03-04 00:00

Strategic Overview

Status: Patched in 2.8.32
Affected Plugin: Contact Form DB
Affected Version: <= 2.8.29
CVSS: 4.3Medium
Weakness type: CWE-352 · Cross-Site Request Forgery (CSRF)
CVE: CVE-2015-1874

View all Contact Form DB vulnerabilities

At a glance

CVE-2015-1874 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Contact Form DB WordPress plugin, affecting versions <= 2.8.29. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.8.32; sites on affected versions should update now. Disclosed March 2015, reported by Tom Adams.

Vulnerability Overview

Cross-site request forgery (CSRF) vulnerability in the Contact Form DB (aka CFDB and contact-form-7-to-database-extension) plugin before 2.8.32 for WordPress allows remote attackers to hijack the authentication of administrators for requests that delete all plugin records via a request in the CF7DBPluginSubmissions page to wp-admin/admin.php.

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 Contact Form DB <= 2.8.29 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 Contact Form DB the fix is 2.8.32: builds <= 2.8.29 are affected, anything from 2.8.32 onward is not.

Remediation

Update to version 2.8.32, or a newer patched version

How does WordSec protect against this?

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

Firewall
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2015-1874 https://www.wordfence.com/threat-intel/vulnerabilities/id/642012fa-28a5-46dc-a68f-3a4ce1cbced3 https://nvd.nist.gov/vuln/detail/CVE-2015-1874

Related records

Other vulnerabilities in Contact Form DB

CVSS Vector

4.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionRequired
ScopeUnchanged
ConfidentialityNone
IntegrityLow
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/