Reflected XSS via unsanitized transaction action
Published Sep 29, 2023 · Updated Apr 28, 2026
Reflected XSS in pensopay Payments 6.3.1 and earlier allows remote attackers to execute browser script through a crafted request. The manual transaction-actions handler fails to sanitize the attacker-controlled pensopay_action parameter before reflecting its value. Exploitation requires a victim to follow the crafted request, enabling script execution in the site's origin and access to browser-visible data.
Summary
What happened
Reflected XSS in pensopay Payments 6.3.1 and earlier allows remote attackers to execute browser script through a crafted request. The manual transaction-actions handler fails to sanitize the attacker-controlled pensopay_action parameter before reflecting its value. Exploitation requires a victim to follow the crafted request, enabling script execution in the site's origin and access to browser-visible data.
The record
- CVE
- CVE-2023-41691
- Published
- Sep 29, 2023
- Updated
- Apr 28, 2026
- Vendor
- pensopay
- Product
- pensopay Payments
- Classifications
- CWE-79, CAPEC-591, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 29, 2023CVE publishedPublication date reported by the CVE source.
- Apr 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=n/a <=6.3.1 changes=[{"at":"6.3.2","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