Session compromise via reflected payment-field scripts
Published Feb 1, 2026 · Updated Feb 1, 2026
Reflected XSS in three CriticalGears Payment Terminal products allows remote authenticated users to execute scripts in users' browsers. Billing and payment fields reflect submitted script code without neutralizing it before browser rendering. Low-privileged access and a victim's display of the crafted response are required; exploitation enables session hijacking or phishing.
Summary
What happened
Reflected XSS in three CriticalGears Payment Terminal products allows remote authenticated users to execute scripts in users' browsers. Billing and payment fields reflect submitted script code without neutralizing it before browser rendering. Low-privileged access and a victim's display of the crafted response are required; exploitation enables session hijacking or phishing.
The record
- CVE
- CVE-2021-47885
- Published
- Feb 1, 2026
- Updated
- Feb 1, 2026
- Vendor
- Authorize.net
- Product
- Authorize.net Payment Terminal
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 1, 2026CVE publishedPublication date reported by the CVE source.
- Feb 1, 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=2.4.1
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
- Payment Terminal 2.x and 3.x multiple XSS proof of conceptproof of concept · unverified
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