Session hijacking via unsanitized payment-method names
Published Mar 24, 2026 · Updated Mar 24, 2026
Stored XSS in Wallos before 4.7.0 allows remote authenticated users to hijack sessions through a renamed payment method. endpoints/payments/rename.php stores the name POST parameter without validate(), and three pages render the value without output escaping. Exploitation requires an authenticated account and a victim page visit; the script can read the non-HttpOnly wallos_login cookie and impersonate that victim.
Summary
What happened
Stored XSS in Wallos before 4.7.0 allows remote authenticated users to hijack sessions through a renamed payment method. endpoints/payments/rename.php stores the name POST parameter without validate(), and three pages render the value without output escaping. Exploitation requires an authenticated account and a victim page visit; the script can read the non-HttpOnly wallos_login cookie and impersonate that victim.
The record
- CVE
- CVE-2026-33400
- Published
- Mar 24, 2026
- Updated
- Mar 24, 2026
- Vendor
- ellite
- Product
- Wallos
- Classifications
- CWE-79, T1539
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 24, 2026CVE publishedPublication date reported by the CVE source.
- Mar 24, 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=< 4.7.0
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
- GHSA-p6v5-227f-f3fv proof of conceptproof 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