# CVE-2026-103312: Payment Integration Wompi <= 4.0.1 - Unauthenticated Payment Confirmation Forgery via IPN Callback


- **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
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-f39h-p64c-xrvv

## What is CVE-2026-103312?

CVE-2026-103312 is a medium-severity vulnerability in Unknown Payment Integration Wompi, published on 27 Oct 2026. 

### Official description

The Payment Integration Wompi WordPress plugin through 4.0.1 does not verify the authenticity of incoming payment notifications on a stock install, because the callback's checksum is keyed on a merchant secret that is empty until it is manually configured, allowing an unauthenticated attacker to forge a notification and mark an arbitrary order as paid.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-103312 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-103312 is a medium-severity vulnerability in Unknown Payment Integration Wompi, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-103312 in the wild and no public exploit code.

Affected product: Unknown Payment Integration Wompi. 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-103312/ (Markdown: https://insights.sbomify.com/CVE-2026-103312/index.md)
```

## Sources

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

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