Database for Contact Form 7, WPforms, Elementor forms <= 1.5.1 - Unauthenticated Arbitrary File Copy/Upload via Elementor Pro Form Upload Field 'raw_value'
The Database for Contact Form 7, WPforms, Elementor forms plugin for WordPress is vulnerable to Arbitrary File Copy via the create_entry_el() function in versions up to, and including, 1.5.1. The function reads raw_value from Elementor Pro's Form_Record object for upload-type fields and passes it directly to PHP's copy() without validating that the value corresponds to a legitimately uploaded file — when no file is present in $_FILES, raw_value reflects the attacker-controlled POST string. copy() accepts both local filesystem paths and URL sources, so the attacker can target any file readable by the PHP process or supply an attacker-controlled remote URL. Elementor Pro is a prerequisite for triggering the code path (it owns the elementor_pro/forms/new_record hook and populates the Form_Record object), but the bug itself is entirely in Contact Form Entries' handler. This could allow unauthenticated attackers to disclose arbitrary files on the affected site's server. The file is copied to a directory unknown to the attacker; the hashed directory name provides defense-in-depth but is generated from non-cryptographic sources (uniqid() + rand()) and should not be relied upon as the primary mitigation.
Quick answer
Database for Contact Form 7, WPforms, Elementor forms should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- *-1.5.1
Fixed versions
- 1.5.2
How to fix it
Database for Contact Form 7, WPforms, Elementor forms is affected by CVE-2026-9145, a the reported vulnerability issue in versions *-1.5.1. Prioritize exposed production sites and users with elevated permissions first. The recommended remediation is to update to version 1.5.2 or a newer vendor-supported patched release. If immediate patching is not possible, reduce exposure, restrict access to the vulnerable workflow, and monitor logs until the vendor-supported fix is in place.
- Inventory every WordPress site that uses Database for Contact Form 7, WPforms, Elementor forms, including production, staging, multisite, customer, and managed environments.
- Confirm the installed plugin or theme version and compare it with versions *-1.5.1 from the linked advisory.
- Apply the remediation: update to version 1.5.2 or a newer vendor-supported patched release.
- If the update cannot be applied immediately, disable Database for Contact Form 7, WPforms, Elementor forms, remove unused roles that can reach the vulnerable feature, and restrict the affected admin, REST, shortcode, upload, booking, ecommerce, review, or content workflow.
- Review application, web server, security plugin, WAF, authentication, and administrator activity logs for attempts related to CVE-2026-9145.
- Rotate administrator sessions, API keys, webhook secrets, database credentials, and integration tokens if logs or file/content review suggest compromise.
- Clear application, object, page, CDN, and browser caches after remediation so vulnerable assets, stored payloads, or stale responses are not served.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm Database for Contact Form 7, WPforms, Elementor forms is no longer running versions *-1.5.1 and record the patched or mitigated version in the remediation ticket.
- Verify unauthenticated, subscriber, contributor, author, editor, shop manager, booking, vendor, or custom-role users can no longer trigger the affected action.
- Review logs before and after the fix for exploitation attempts, unexpected content changes, suspicious admin actions, or database/file access.
- Rerun a Fixnx scan and any relevant plugin, WAF, or manual regression checks to confirm public exposure is reduced.
- Document the advisory link, affected assets, remediation action, verification evidence, and any cleanup or credential rotation performed.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-9145?
Database for Contact Form 7, WPforms, Elementor forms versions listed as affected should be reviewed: *-1.5.1.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.