CVE-2026-103312VulnerabilityPublished 27 Oct 2026

The Payment Integration Wompi WordPress plugin through 4.0.1 does not verify the authenticity of incoming payment

Source GCVE Database

Authoritative record:CVE-2026-103312· High

Not known to be exploited.

Data as of 27 Oct 2026, 07:44 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-f39h-p64c-xrvv

What to do

Affected software

Product	Affected	Fixed in
Payment Integration Wompi	Affected <=4.0.1	Fixed in–

AI-suggested

Users should manually configure the merchant secret to enable proper verification of payment notifications.

Description

The Payment Integration Wompi WordPress plugin up to version 4.0.1 fails to verify the authenticity of incoming payment notifications by default. This occurs because the callback's checksum relies on a merchant secret that is empty until manually configured. As a result, an unauthenticated attacker can forge payment notifications and mark arbitrary orders as paid.

References

Community reviews

Loading reviews…