Contributor-level JavaScript execution via unsanitized form labels
Published Jun 21, 2021 · Updated Aug 3, 2024
Stored XSS in GetPaid before 2.3.4 allows remote authenticated users to execute JavaScript through crafted payment-form fields. The payment-form editor stores Label and Help Text values without adequate sanitization and executes injected markup during its live backend render. Contributor access is sufficient to submit the content, while an administrator's later review can execute it and permit creation of a rogue administrator account.
Summary
What happened
Stored XSS in GetPaid before 2.3.4 allows remote authenticated users to execute JavaScript through crafted payment-form fields. The payment-form editor stores Label and Help Text values without adequate sanitization and executes injected markup during its live backend render. Contributor access is sufficient to submit the content, while an administrator's later review can execute it and permit creation of a rogue administrator account.
The record
- CVE
- CVE-2021-24369
- Published
- Jun 21, 2021
- Updated
- Aug 3, 2024
- Vendor
- AyeCode Ltd
- Product
- GetPaid
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 21, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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.3.4 <2.3.4
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
- WPScan GetPaid stored-XSS reproduction procedureproof 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