Cleverbridge: third party copied stored payment card data (reportedly incl. CVV/CVC)
Severity: high · Patch status: no-fix-needed · Since 2026-11-22
Cleverbridge, an e-commerce and subscription-billing platform for software and SaaS merchants, says it detected unauthorised activity on its platform on 4 November 2026, took affected systems offline and had them back the same day. Its incident page says a third party copied payment card data stored on the platform, and that card details used to buy through Cleverbridge may be involved; it also says none of its systems were encrypted, so this was not ransomware. Customer notices began on 20 November, with credit or identity monitoring offered through TransUnion's Cyberscout where available. Cleverbridge has not said how many customers were affected, how the attacker got in, or how long it was present. BleepingComputer reports, quoting a breach notice it obtained, that the copied data was card numbers, expiry dates and CVV/CVC codes, and not names or billing details. Cleverbridge's public page does not list those fields, and no regulator filing or second source was found for the CVV/CVC part. Affected cardholders should review statements and contact their issuers; issuers can replace cards where CVV/CVC exposure is confirmed.
What to do
- Identify customers whose payment cards were used through Cleverbridge and tell them to review statements for unauthorized charges.
- Advise affected cardholders to contact their card issuers; if CVV/CVC exposure is confirmed for a card, the issuer may replace it.
- Monitor for fraud and phishing referencing Cleverbridge or the breach.
- Review third-party payment and e-commerce vendor risk, including PCI DSS scope and whether CVV/CVC storage is permitted.
- Verify Cleverbridge notification details and preserve relevant logs if investigating.
Sources
All live incidents on Threat Watch