Skip to main content

WPForms CVE-2026-48835

| EUVDEUVD-2026-36843 HIGH
Missing Authorization (CWE-862)
2026-06-15 Patchstack GHSA-xhpp-7jwj-prh5
7.5
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify WordPress site running WPForms ≤ 1.10.0.4
  2. Delivery
    Send unauthenticated request to vulnerable AJAX/REST handler
  3. Exploit
    Bypass missing authorization check
  4. Execution
    Invoke privileged plugin action
  5. Impact
    Tamper with form or plugin data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

No special conditions are required beyond network reachability of a WordPress site running Contact Form by WPForms (wpforms-lite) at version 1.10.0.4 or earlier with the plugin active; per the CVSS vector (AV:N/AC:L/PR:N/UI:N), exploitation is remote, low-complexity, unauthenticated, and needs no user interaction. Limiting factors are that the plugin must actually be installed and activated on a reachable endpoint, and the impact is restricted to integrity - the flaw does not directly disclose data or take the site offline, so sites that proxy WordPress behind an authenticating reverse proxy, IP-restrict admin-ajax.php / wp-json, or have already updated past 1.10.0.4 are not exposed.

Impact

The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, base 7.5) describes a network-reachable, low-complexity, unauthenticated path with high integrity impact only - confidentiality and availability are unaffected, which is consistent with an access-control flaw that lets attackers tamper with plugin state rather than read data or crash the site. KEV status is not asserted in the input and no POC is referenced, so this should be treated as a high-severity but not confirmed actively exploited issue; EPSS is not provided, preventing quantitative exploitation-probability comparison. The very large install base of WPForms and the trivially low attack complexity argue for prompt patching even without exploitation telemetry, but the precise affected endpoint and the concrete integrity action attackers can perform are not disclosed in the Patchstack summary - defenders should consult the Patchstack advisory for specifics before scoping mitigation.

Exploit ScenarioDerived

An unauthenticated attacker sends a crafted HTTP POST to a vulnerable WPForms AJAX or REST endpoint on a target WordPress site, invoking a privileged operation that should be limited to administrators - for example modifying a form, altering submission handling, or changing plugin configuration. Because the handler lacks an authorization check, the request succeeds anonymously and the attacker tampers with site data (CVSS I:H) without ever logging in. No public proof-of-concept is referenced in the provided data.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 15, 2026

Broken access control in the Contact Form by WPForms plugin (versions <= 1.10.0.4) for WordPress allows remote unauthenticated attackers to perform unauthorized actions affecting data integrity. The flaw stems from missing authorization checks (CWE-862) on plugin functionality, enabling tampering without any credentials or user interaction. No public exploit identified at time of analysis, and EPSS data was not provided in the input.

RemediationAI

Upgrade Contact Form by WPForms to a version newer than 1.10.0.4 via the WordPress plugin updater as soon as a fixed release is published; consult the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/wpforms-lite/vulnerability/wordpress-contact-form-by-wpforms-plugin-1-10-0-4-broken-access-control-vulnerability) for the exact patched version, as the input data does not name one. Patch available per vendor advisory but exact fix version is not independently confirmed from the provided data. Until the update is applied, compensating controls include restricting access to /wp-admin/admin-ajax.php and the WordPress REST API endpoints exposed by WPForms via a WAF rule or Patchstack/Wordfence virtual patch, temporarily deactivating the plugin if the form functionality is non-critical (side effect: contact forms stop rendering and submissions are lost), or scoping IP allow-lists to admin-area requests (side effect: may break legitimate front-end form submissions if applied too broadly). Audit form configurations, submitted entries, and plugin settings for unexpected changes after exposure.

Affected VersionsENISA

Contact Form by WPForms n/a ≤1.10.0.4

Affected Packages

euvd contact_form_by_wpforms no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

WPForms (also known as Contact Form by WPForms / wpforms-lite) is one of the most widely deployed WordPress form-builder plugins, developed by Awesome Motive (CPE: awesomemotive:contact_form_by_wpforms). The root cause is CWE-862 (Missing Authorization), meaning one or more plugin endpoints - typically exposed via WordPress AJAX or REST handlers - execute privileged operations without verifying the caller's capability (e.g., current_user_can) or nonce. Because WordPress plugins commonly register admin-ajax.php actions that are reachable by anonymous users when the underlying handler omits an authorization gate, an unauthenticated HTTP request alone is sufficient to invoke the affected functionality.

Know when Contact Form By Wpforms gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
vuln.today AI 7.5 HIGH

Unauthenticated network request to a WordPress plugin endpoint missing authorization checks; integrity-only impact per CWE-862 access-control bypass, no confidentiality or availability effect described.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

DescriptionCVE.org

Unauthenticated Broken Access Control in Contact Form by WPForms <= 1.10.0.4 versions.

Executive ViewAI

Why It Matters

Contact Form by WPForms plugin for WordPress (versions ≤1.10.0.4) contains a broken access control vulnerability (CVSS 7.5) allowing unauthenticated attackers to manipulate form functionality without authorization. No public exploit identified at time of analysis, but organizations using WPForms risk unauthorized access to customer data and operational disruption. WordPress sites hosting customer inquiries, registrations, or payments require immediate remediation to protect data integrity and business continuity.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) disable the WPForms plugin and migrate form functionality to alternative providers on non-critical systems, (2) restrict form endpoint access via Web Application Firewall IP allowlisting or reverse proxy authentication to limit exposure, (3) implement enhanced audit logging and real-time alerting on form submissions and related database modifications, (4) conduct daily automated integrity checks on form submission data to detect unauthorized changes, (5) maintain backup and recovery procedures for form data to enable rapid restoration in case of compromise.

Threat Intelligence Overview

EPSS Score
0.3%
Top 78% exploitable
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy