What is the CVSS score of EUVD-2026-34954?

EUVD-2026-34954 has a CVSS 3.1 base score of 5.3 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N. EPSS exploitation probability: 0.0%.

WPForms EUVD-2026-34954

| CVE-2026-7792 MEDIUM

Insufficient Verification of Data Authenticity (CWE-345)

2026-06-06 Wordfence

GHSA-46hc-3pvv-7xv3

WordPress Information Disclosure Wordpress Plugin Wpforms Easy Form Builder For Wordpress Contact Forms Payment Forms Surveys More Smub

5.3

CVSS 3.1 · Vendor: Wordfence

View

Attack ChainAIDerived

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

Access

Identify target site running WPForms PayPal Commerce
Delivery

Obtain valid PayPal subscription_id
Exploit

Craft JSON payload with whitelisted event_type
Execution

POST forged webhook to public endpoint
Persist

Bypass absent HMAC-SHA256 verification
Impact

Subscription handler sets status to active

Vulnerability Assessment

Weakness	CWE CWE-345 OWASP Top 10:2025 A08:2025 - Software or Data Integrity Failures ASVS 5.0 V15 - Secure Coding and Architecture Data authenticity verification
Exploitation Conditions	Exploitation requires that the WPForms PayPal Commerce payment integration is actively configured on the target WordPress installation - sites using Stripe, Authorize.Net, Square, or no payment integration expose no vulnerable endpoint and are completely unaffected. The attacker must possess a valid PayPal subscription_id associated with a subscription registered on the specific target site; without this, the forged resource data will reference a non-existent subscription and handlers will produce no useful outcome. The CVSS vector PR:N/UI:N confirms that once a valid subscription_id is in hand, no authentication, session, or user interaction is required. Exploitation is scoped exclusively to subscription payment record manipulation - the CVSS vector C:N/A:N confirms no confidentiality exposure (no data leakage) and no availability impact (no denial of service). The webhook endpoint is intentionally internet-accessible to receive callbacks from PayPal, so no network-level bypass is required.
Impact	The CVSS 5.3 Medium score (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N) correctly reflects remote, unauthenticated, zero-interaction access with limited integrity impact at the NVD scoring level, but the business impact materially exceeds what the integrity:Low designation implies - the vulnerability directly enables payment fraud by allowing subscription access to be restored without payment. EPSS data was not provided in the input and cannot be assessed. The vulnerability is not listed in CISA KEV and no publicly available POC has been identified, meaning exploitation risk is currently inferred rather than confirmed. The primary attack complexity factor not captured in the AC:L rating is the prerequisite of knowing a valid PayPal subscription_id for the target site, which is a non-trivial information requirement that meaningfully reduces opportunistic mass exploitation risk. Sites that have not enabled the WPForms PayPal Commerce integration are entirely unexposed - this significantly narrows the affected population. A patched version (1.10.0.4) is confirmed available in the WordPress SVN repository, lowering urgency for sites that update promptly. Overall priority is medium-high for sites running WPForms with active PayPal Commerce subscriptions; low for all others.
Exploit ScenarioDerived	An attacker targeting a WordPress e-commerce site running WPForms with PayPal Commerce subscriptions first obtains a valid PayPal subscription_id - either through a legitimate low-cost purchase on the target site, prior access, or enumeration - then constructs a JSON POST request with a whitelisted event_type such as BILLING.SUBSCRIPTION.ACTIVATED and a resource body setting subscription_status to active, submitted directly to the site's WPForms PayPal Commerce webhook endpoint with no authentication. No public POC has been identified, but the attack requires only standard HTTP tooling and knowledge of the endpoint path, making independent replication feasible for any attacker with a valid subscription_id.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).

No patch listed yet 0.0% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Jun 06, 2026

Unauthenticated webhook forgery in WPForms (wpforms-lite ≤1.10.0.1) enables payment fraud by allowing any remote attacker who knows a valid PayPal subscription_id to manipulate subscription payment records - including forcing a cancelled or suspended subscription back to active status - without any credentials or user interaction. The PayPal Commerce webhook endpoint accepts and acts on arbitrary JSON POST payloads, performing no HMAC-SHA256 origin verification, and trusts attacker-supplied resource data once the event_type field passes a whitelist check. No public exploit has been identified and this vulnerability is not listed in CISA KEV at time of analysis, but the zero-complexity attack path makes independent exploitation straightforward for anyone possessing a valid subscription_id.

RemediationAI

Upgrade wpforms-lite to version 1.10.0.4 or later immediately; this version is confirmed patched based on the WordPress plugin SVN changeset 3532389, which modifies WebhookRoute.php to add proper HMAC-SHA256 signature verification before any payload processing. WordPress site operators can update via the Plugins dashboard or WP-CLI (wp plugin update wpforms-lite). If immediate upgrade is not feasible, the most effective compensating control is to disable the PayPal Commerce payment integration in WPForms settings (WPForms > Settings > Payments > PayPal Commerce), which prevents the vulnerable webhook endpoint from receiving any external traffic; the trade-off is that PayPal Commerce payment processing will be suspended until the patch is applied. A secondary control - configuring WAF rules to restrict POST access to the wpforms PayPal webhook route exclusively to known PayPal IP ranges - is possible but operationally fragile, as PayPal's egress IP space can change without notice and requires ongoing maintenance. References: Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/d5cf5fd2-58c7-42d0-948f-95764647630b; patched code at https://plugins.trac.wordpress.org/changeset/3532389/wpforms-lite/trunk/src/Integrations/PayPalCommerce/Api/WebhookRoute.php.

Affected VersionsENISA

WPForms – Easy Form Builder for WordPress – Contact Forms, Payment Forms, Surveys, & More 0 ≤1.10.0.4

Affected Packages

euvd wpforms_easy_form_builder_for_wordpress_contact_forms_payment_forms_surveys_more 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

The affected component is the PayPal Commerce webhook integration within wpforms-lite (CPE: cpe:2.3:a:smub:wpforms_-_easy_form_builder_for_wordpress_-_contact_forms,_payment_forms,_surveys,_&_more:*:*:*:*:*:*:*:*). PayPal's Commerce platform requires webhook recipients to validate an HMAC-SHA256 signature transmitted in the request headers, computed from the raw payload body using a secret known only to the legitimate recipient - this is the standard cryptographic mechanism to prove that a webhook originated from PayPal infrastructure. In WPForms ≤1.10.0.1, the WebhookRoute.php handler (lines L122 and L170 in the SVN repository) skips this verification entirely. The only gate applied is a check that the supplied event_type value appears in a whitelist, after which the attacker-controlled resource object from the JSON body is passed verbatim to downstream handlers including BillingSubscriptionActivated.php:L38 and BillingSubscriptionCancelled.php:L32, which update subscription payment records based on the untrusted data. CWE-345 (Insufficient Verification of Data Authenticity) precisely describes this root cause: the system acts on data claiming to originate from a trusted third party (PayPal) without cryptographically proving that claim.

Know when Wordpress Plugin 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

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

Vendor (Wordfence) PRIMARY 5.3 MEDIUM

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

Primary rating from Vendor (Wordfence) · only source for this CVE.

CVSS VectorVendor: Wordfence

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

DescriptionCVE.org

The WPForms - Easy Form Builder for WordPress - Contact Forms, Payment Forms, Surveys, & More plugin for WordPress is vulnerable to Insufficient Verification of Data Authenticity in versions up to and including 1.10.0.1. This is due to the PayPal Commerce webhook endpoint processing unauthenticated JSON webhook payloads without verifying that the request originated from PayPal using the required HMAC-SHA256 webhook signature, and only checking whether the supplied event_type is whitelisted before dispatching the attacker-controlled resource data to handlers that update payment records. This makes it possible for unauthenticated attackers who know a valid PayPal subscription_id to forge PayPal webhook events and modify subscription payment records, such as reactivating a cancelled or suspended subscription by setting its subscription_status to active.

Threat Intelligence Overview

EPSS Score

0.0%

Top 88% exploitable

Social Media

Sightings

Data Quality

6 sources

Confidence: High

EUVD

NVD

CVE.org

EPSS

Vulnrichment CIRCL

VulDB

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 MEDIUM

CISA KEV No

Public POC No

EPSS 0.0%

Patch available No

Active threat No

Deciding rule

MEDIUM severity (CVSS 4.0-6.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· derived

Scheduled

Exploitation

None

System Exposure· derived

Open

Automatable

Yes

Human Impact· derived

Medium

Technical Impact

Partial

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +26

PoC: 0

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Information Disclosure MEDIUM

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.