# CVE-2026-1782: MetForm Pro <= 3.9.7 - Unauthenticated Payment Amount Manipulation via 'mf-calculation'

> Unauthenticated attackers can manipulate payment amounts in MetForm Pro by submitting invalid calculation values, bypassing price validation.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Apr 2026
- **Updated:** 15 Apr 2026
- **Also known as:** GHSA-q72v-prr3-m2r8

## What is CVE-2026-1782?

CVE-2026-1782 is a medium-severity vulnerability in Wpmet MetForm Pro, published on 15 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-1782?


## How do I fix CVE-2026-1782?

No fix has been published for CVE-2026-1782 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-1782 being exploited?

There is no known exploitation of CVE-2026-1782 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1782 and fix it if it is affected.

What it is: CVE-2026-1782 is a medium-severity vulnerability in Wpmet MetForm Pro, published on 15 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-1782 in the wild and no public exploit code.

Affected product: Wpmet MetForm Pro. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-1782/ (Markdown: https://insights.sbomify.com/CVE-2026-1782/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-1782
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1782
- OSV: https://osv.dev/vulnerability/CVE-2026-1782

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-1782/
Summaries are generated and may contain mistakes; the official description above is the record.