Payment bypass via unsigned offsite return
Published Jan 28, 2026 · Updated Jan 28, 2026
Authentication bypass in Drupal Commerce Paybox 7.x-1.0 through 7.x-1.5 allows remote attackers to complete orders without payment. The offsite return handler accepts a crafted callback with a bogus sig value before IPN confirmation and changes a pending payment to successful instead of verifying the Paybox signature. No account or user interaction is required, but a pending Commerce order and a network-reachable return endpoint are required; the result is fraudulent transaction completion.
Summary
What happened
Authentication bypass in Drupal Commerce Paybox 7.x-1.0 through 7.x-1.5 allows remote attackers to complete orders without payment. The offsite return handler accepts a crafted callback with a bogus sig value before IPN confirmation and changes a pending payment to successful instead of verifying the Paybox signature. No account or user interaction is required, but a pending Commerce order and a network-reachable return endpoint are required; the result is fraudulent transaction completion.
The record
- CVE
- CVE-2026-0750
- Published
- Jan 28, 2026
- Updated
- Jan 28, 2026
- Vendor
- Avatar Uploader Project
- Product
- Commerce Paybox
- Classifications
- CWE-347, CAPEC-115, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 28, 2026CVE publishedPublication date reported by the CVE source.
- Jan 28, 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=7-x-1.0 <=7.x-1.5
What conditions does exploitation require?
What is affected?
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
- HeroDevs forged return-flow reproductionproof of concept · demonstrated
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