Payment-status forgery via exposed transaction ticket
Published Aug 13, 2026 · Updated Aug 13, 2026
Missing authorization in Secure Card Gateway 1.0.32 and earlier allows remote attackers to forge paid order status via a crafted callback. The redirect form exposes the TranTicket, which serves as the HMAC-SHA256 key, letting a shopper compute a valid HashKey for the callback. Exploitation requires a shopper to initiate a payment for an order; the forged callback can mark that order paid without a matching bank settlement.
Summary
What happened
Missing authorization in Secure Card Gateway 1.0.32 and earlier allows remote attackers to forge paid order status via a crafted callback. The redirect form exposes the TranTicket, which serves as the HMAC-SHA256 key, letting a shopper compute a valid HashKey for the callback. Exploitation requires a shopper to initiate a payment for an order; the forged callback can mark that order paid without a matching bank settlement.
The record
- CVE
- CVE-2026-61978
- Published
- Aug 13, 2026
- Updated
- Aug 13, 2026
- Vendor
- WebHosting4U
- Product
- Secure Card Gateway for ePay Paycenter (Piraeus Bank)
- Classifications
- CWE-862, CAPEC-180, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 13, 2026CVE publishedPublication date reported by the CVE source.
- Aug 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=n/a <=1.0.32 changes=[{"at":"1.0.33","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo