dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2026-1782

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The MetForm Pro plugin for WordPress fails to validate payment amounts server-side. Attackers can submit a manipulated 'mf-calculation' field value in REST API requests to override the intended form price, allowing them to set arbitrary payment amounts. The payment integrations (Stripe/PayPal) trust client-submitted calculation values without recomputing or validating them against the configured form price.

MitigationUpdate the plugin beyond version 3.9.7 when a patch is available. Until then, review and restrict forms using payment integrations, and implement server-side validation of calculation fields to ensure payment amounts match configured prices.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm MetForm Pro plugin is installed
    Check for the presence of the metform-pro directory in wp-content/plugins/ or look for MetForm Pro in WordPress admin under Plugins
    Affected if The plugin is installed and active
  2. Identify installed MetForm Pro version
    View the plugin file header (usually main plugin file or readme.txt) to read the Version: field, or check via WordPress plugin admin page
    Affected if Version is 3.9.7 or lower (prior to any available patch)
  3. Check for active payment integrations
    Review configured forms in MetForm > All Forms and verify if any forms have Stripe or PayPal payment elements enabled in form settings
    Affected if Any form has Stripe or PayPal payment integration enabled and active
  4. Identify forms using mf-calculation field for pricing
    Examine form configurations to detect if mf-calculation fields are used to compute payment amounts, particularly where the calculated value drives the final payment
    Affected if Forms use mf-calculation field to dynamically set payment amounts that feed into payment integrations

A user is affected if MetForm Pro version 3.9.7 or lower is installed AND forms with active Stripe/PayPal payment integrations exist that rely on mf-calculation fields for pricing.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin beyond version 3.9.7 when a patch is available. Until then, review and restrict forms using payment integrations, and implement server-side validation of calculation fields to ensure payment amounts match configured prices.

Recommended fix Moderate confidence

Latest available MetForm Pro release (version 3.9.8 or higher)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate MetForm Pro in the plugin list
  4. 4. Check the current installed version to confirm it is 3.9.7 or below
  5. 5. Navigate to Dashboard > Updates or check wpmet.com for the latest MetForm Pro release
  6. 6. Update MetForm Pro to the latest available version (likely 3.9.8 or higher)
  7. 7. After updating, verify the payment form settings in MetForm to confirm calculation fields are properly validated
  8. 8. Test a form submission with a payment integration (Stripe/PayPal) to confirm the price is computed server-side and cannot be manipulated via the mf-calculation field
Caveat Minor: Review any custom calculation formulas after upgrade to ensure compatibility with new server-side validation

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1782 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1782 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data