Skip to main content

Metform Pro EUVDEUVD-2026-22851

| CVE-2026-1782 MEDIUM
Improper Input Validation (CWE-20)
2026-04-15 Wordfence
5.3
CVSS 3.1 · NVD
View

Attack ChainAIDerived

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

  1. Access
    Identify vulnerable MetForm form endpoint
  2. Delivery
    Craft REST POST with 'mf-calculation' parameter
  3. Exploit
    Submit form to payment gateway
  4. Execution
    Execute charge at altered amount
  5. Impact
    Complete fraudulent transaction

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
Impact

The CVSS 5.3 score reflects a network-based attack (AV:N) with low complexity (AC:L) requiring no authentication (PR:N) or user interaction (UI:N). The integrity impact (I:L) is rated as low rather than high because the vulnerability affects the integrity of payment data rather than broader system integrity. However, real-world risk is substantially higher than the moderate CVSS rating suggests. This is a direct financial fraud vector affecting e-commerce workflows: attackers can reduce invoice amounts, avoid payment obligations, or manipulate refund values. The lack of authentication requirement and trivial attack complexity mean any visitor to a vulnerable form can exploit this. EPSS and KEV status are not provided, but the absence of reported active exploitation at analysis time does not diminish priority-payment fraud vulnerabilities are immediately valuable to attackers and likely to be exploited opportunistically. The SSVC framework would rank this as 'Immediate' due to automatable exploitation of a form-handling function affecting multiple payment platforms. For organizations relying on MetForm Pro for transactions, this warrants urgent patching despite the moderate CVSS.

Exploit ScenarioDerived

An attacker identifies a WordPress site using MetForm Pro with a product purchase form configured to accept Stripe payments. The form includes a price field calculated based on product selection. The attacker intercepts or crafts a direct REST API request to the form endpoint with a malicious 'mf-calculation' value set to '0.01' instead of the legitimate product price (e.g., '99.99'). The form submission processes successfully, and Stripe charges the victim's payment method only $0.01 instead of the full amount, while the attacker receives the product or service.

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 – Apr 15, 2026

Remote attackers can manipulate payment amounts in Stripe and PayPal transactions through the MetForm Pro WordPress plugin by submitting arbitrary values in the 'mf-calculation' field, bypassing price validation. Versions up to 3.9.7 are affected; the plugin fails to recompute or validate user-submitted calculation fields against configured form prices, allowing unauthenticated attackers to reduce or alter payment amounts on vulnerable forms. No active exploitation has been publicly confirmed, though the attack requires minimal complexity and produces direct financial impact.

RemediationAI

Update MetForm Pro to a patched version released after 3.9.7 via the WordPress plugin dashboard or directly from https://wpmet.com/plugin/metform/. The vendor has released a fix; administrators should check the plugin's changelog for the first patched release following version 3.9.7 and apply it immediately to all affected installations. As a temporary workaround prior to patching, disable payment integration forms or restrict form access via user role/authentication controls, though this is not a complete mitigation. Verify that any payment transactions processed via vulnerable versions are audited for discrepancies. Review transaction logs in Stripe and PayPal dashboards for suspicious amount modifications during the exposure window.

Affected VersionsENISA

MetForm Pro 0 ≤3.9.7

Affected Packages

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

MetForm Pro is a WordPress form builder plugin that integrates with payment gateways (Stripe and PayPal). The vulnerability stems from improper input validation (CWE-20) in the REST API payment form submission handler. When a form includes price calculation or payment integration, the plugin accepts the 'mf-calculation' field value directly from the client-side form submission without server-side recomputation or validation. This allows an attacker to craft a malicious REST request containing an arbitrary 'mf-calculation' value, which the payment integration then processes as the legitimate transaction amount. The root cause is trust of untrusted user input without cryptographic or logical verification against the form's configured pricing rules. CPE identifier cpe:2.3:a:wpmet:metform_pro:*:*:*:*:*:*:*:* indicates the vulnerability affects all versions of the wpmet MetForm Pro product.

Know when Metform Pro 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

NVD PRIMARY 5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

DescriptionCVE.org

The MetForm Pro plugin for WordPress is vulnerable to Improper Input Validation in all versions up to, and including, 3.9.7 This is due to the payment integrations (Stripe/PayPal) trusting a user-submitted calculation field value without recomputing or validating it against the configured form price. This makes it possible for unauthenticated attackers to manipulate the payment amount via the 'mf-calculation' field in the form submission REST request granted there exists a specific form with this particular configuration.

Threat Intelligence Overview

EPSS Score
0.0%
Top 87% 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 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

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

Attack Technique

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

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