CVE-2026-48835: Unauthenticated Access Control Flaw in WPForms Contact Forms
A flaw in Contact Form by WPForms versions 1.10.0.4 and earlier allows attackers to bypass authentication and modify contact form data without permission. Because no login is required and the vulnerability is straightforward to trigger over the network, any attacker can exploit it. The flaw does not expose sensitive data directly, but enables unauthorized changes to form submissions and settings, disrupting business processes and data integrity.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 7.5 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- Weaknesses (CWE)
- CWE-862
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-06-15 / 2026-06-17
NVD description (verbatim)
Unauthenticated Broken Access Control in Contact Form by WPForms <= 1.10.0.4 versions.
1 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-48835 is an unauthenticated broken access control vulnerability (CWE-862) in Contact Form by WPForms up to version 1.10.0.4. The CVSS 3.1 score of 7.5 (HIGH) reflects a network-accessible attack requiring no privileges or user interaction, with high integrity impact but no confidentiality or availability impact. The vulnerability permits unauthorized modification of contact form data and configurations without prior authentication, likely stemming from insufficient authorization checks on form-related API endpoints or administrative functions.
Business impact
Organizations relying on WPForms contact forms for customer inquiries, lead capture, or critical business communications face data integrity risks. Attackers can alter form submissions, inject malicious content, or corrupt legitimate contact records. This undermines trust in submitted data, complicates compliance audits, and can disrupt workflows dependent on accurate form capture. For businesses using WPForms as a primary contact mechanism, the inability to trust form integrity has immediate operational consequences.
Affected systems
All WordPress installations running Contact Form by WPForms version 1.10.0.4 or earlier are vulnerable. This includes sites using WPForms as a standalone contact form plugin or integrated into broader form management workflows. The vulnerability affects both single-site and multi-site WordPress deployments with the affected plugin versions active.
Exploitability
This vulnerability is highly exploitable. It requires no authentication, no special configuration, and can be triggered via simple HTTP requests from the public internet. The low attack complexity and absence of user interaction requirements mean that automated scanning and exploitation at scale are trivial. No specialized tools or deep plugin knowledge is necessary for an attacker to begin modifying form data.
Remediation
Immediately update Contact Form by WPForms to a version newer than 1.10.0.4. Verify the patch version against the official WPForms advisory or plugin repository to confirm the security update has addressed CWE-862. After patching, audit form submissions and settings for unauthorized modifications made during the vulnerability window. Consider temporarily disabling WPForms contact forms on production sites until patching is confirmed complete.
Patch guidance
1. Log into your WordPress admin dashboard and navigate to Plugins → Installed Plugins. 2. Locate 'Contact Form by WPForms' and check its current version. 3. If version is 1.10.0.4 or earlier, click 'Update now' to apply the latest patch. 4. Verify the new version number matches the patched release (verify against vendor advisory). 5. Test contact forms in a staging environment before confirming on production. 6. Document the patching date and version number for compliance records.
Detection guidance
Monitor web server and WordPress logs for suspicious POST/GET requests to form-related endpoints (typically /wp-admin/admin-ajax.php with form action parameters). Look for requests lacking valid nonces, session tokens, or authentication headers that successfully modify form data. Enable WordPress security logging plugins to capture unauthorized form submissions. Check form submission history for anomalous entries created outside normal business hours or from unexpected IP addresses. Review contact form settings and saved submissions for unexpected changes.
Why prioritize this
This vulnerability merits urgent patching due to the combination of high CVSS score (7.5), zero authentication requirements, and network accessibility. The integrity impact on form data directly affects business operations. Unlike vulnerabilities requiring user interaction or valid credentials, this flaw can be exploited immediately and at scale against any exposed WPForms instance. The lack of confidentiality impact prevents it from being critical, but the integrity breach justifies immediate remediation.
Risk score, explained
The CVSS 3.1 score of 7.5 reflects: network-accessible attack vector (AV:N), low attack complexity (AC:L), no privilege requirement (PR:N), no user interaction needed (UI:N), unchanged scope (S:U), no confidentiality impact (C:N), high integrity impact (I:H), and no availability impact (A:N). The HIGH severity is driven by the trivial exploit path and significant integrity damage, though lack of data exposure and system availability impact prevent a critical rating.
Frequently asked questions
Can we safely keep WPForms running if we restrict form access by IP or disable it temporarily?
Restricting IP access provides some mitigation but is not a substitute for patching. If WPForms must remain active before patching, disable public access to the plugin via web server rules or WordPress security plugins. However, this is a temporary workaround only—patch immediately to restore functionality safely.
Do we need to audit all historical form submissions, or only recent ones?
Audit submissions created after the vulnerability was published (2026-06-15) or since you became aware of the vulnerability, whichever is earlier. If you cannot determine when exploitation began, audit back at least 30 days or to your last security baseline. Focus on entries with suspicious content, malformed data, or timestamps outside normal hours.
Will patching WPForms cause data loss or break existing forms?
Standard plugin updates do not delete form data or submissions. After patching, verify that existing forms display correctly and new submissions are captured as expected. Test on a staging environment first if possible. Back up your WordPress database before patching as a precaution.
Is this vulnerability included in any known exploit kits or ransomware campaigns?
This vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and has not been observed in active ransomware campaigns as of the publication date. However, given its ease of exploitation, widespread WordPress plugin usage, and integrity impact, it is a prime candidate for opportunistic abuse and merits rapid patching regardless.
This analysis is based on vendor advisory data and public CVE information as of 2026-06-17. Specific patch versions, availability, and release timelines should be verified directly with WPForms' official security advisories and plugin repository. SEC.co does not provide legal advice or guarantee the completeness of remediation steps; organizations should validate patch deployment in their environment and consult their security team. No exploit code or weaponized proof-of-concept is provided in this analysis. Source: NVD (public-domain), retrieved 2026-07-24. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2018-25391HIGHHaPe PKH 1.1 Authorization Bypass – Unauthorized Record Deletion Vulnerability
- CVE-2025-26418HIGHAndroid CarDevicePolicyService Privilege Escalation (CVSS 7.8)
- CVE-2025-53345HIGHThimPress Thim Core Missing Authorization Leads to Code Execution
- CVE-2026-0133HIGHAndroid ARM SMMU v3 Privilege Escalation (CVSS 7.8)
- CVE-2026-0272HIGHPalo Alto PAN-OS Privilege Escalation Vulnerability (PA-Series, VM-Series, Panorama)
- CVE-2026-10737HIGHWordPress SP Project & Document Manager Unauthenticated File Access Vulnerability
- CVE-2026-26236HIGHQuMagie Missing Authorization Vulnerability – Patch to 2.9.0
- CVE-2026-26237HIGHQuMagie Missing Authorization Vulnerability – HIGH Severity Data Exposure