# CVE-2026-122062: Pronamic Pay & Pronamic Pay doneren met Mollie - Unauthenticated Form Submission Disclosure via REST API


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 8 Nov 2026
- **Updated:** 8 Nov 2026
- **Also known as:** GHSA-4435-94rm-8hr8

## What is CVE-2026-122062?

CVE-2026-122062 is a medium-severity vulnerability in Unknown Pronamic Pay, published on 8 Nov 2026. 

### Official description

The Pronamic Pay WordPress plugin before 11.1.0, Pronamic Pay doneren met Mollie WordPress plugin before 1.7.1 do not restrict access to stored form submissions through the REST API, allowing unauthenticated users to read the messages that visitors submitted through the bundled forms.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-122062 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-122062 is a medium-severity vulnerability in Unknown Pronamic Pay, published on 8 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-122062 in the wild and no public exploit code.

Affected product: Unknown Pronamic Pay. 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-122062/ (Markdown: https://insights.sbomify.com/CVE-2026-122062/index.md)
```

## Sources

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

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