CVE-2026-119038: Business-GoCardless (Perl module) · Insecure Direct Object Reference
Affects Business-GoCardless (Perl module)Source CVE Database V5
Not known to be exploited : upgrade to 1.01 soon.
Data as of 30 Oct 2026, 13:18 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 1.01
Exploitation evidence
Disclosed: evidence found.
CVE published 30 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 Oct 2026.
What to do
Upgrade Business-GoCardless (Perl module) to 1.01.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Business-GoCardless | Affected
| Fixed in
|
CPANBusiness-GoCardlesspkg:cpan/Business-GoCardlessOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Business-GoCardless to version 1.01 or later, where this authorization bypass vulnerability is fixed. The fix ensures proper session token validation when completing redirect flows. No other mitigation is required as the vulnerability is resolved in the official patch.
Description
Business-GoCardless versions before 1.01 for Perl contain an authorization bypass vulnerability where the redirect flow ID is not properly validated against the user session. This allows an attacker who obtains another customer's redirect flow ID to create payments or subscriptions against that customer's mandate without authorization. The flaw exists because the confirm_resource function does not verify the session token and completes redirect flows solely based on the redirect flow ID returned by the GoCardless API. The issue was fixed in version 1.01.