CVE-2026-103312: Payment Integration Wompi (WordPress plugin) · Improper Authentication
Affects Payment Integration Wompi (WordPress plugin)Source CVE Database V5
Not known to be exploited.
Data as of 27 Oct 2026, 06:27 UTC
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.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Payment Integration Wompi | Affected
| Fixed in– |
AI-suggested
Administrators should manually configure a strong merchant secret in the plugin settings to ensure the callback checksum is properly keyed and verified. Monitor vendor advisories for any future official fixes.
Description
The Payment Integration Wompi WordPress plugin versions up to 4.0.1 does not verify the authenticity of incoming payment notifications by default. This is due to the callback checksum relying 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.