Stored XSS via unvalidated profile fields
Published Feb 29, 2024 · Updated Aug 5, 2024
Stored XSS in JHPyle docassemble before 1.4.97 allows remote attackers to execute JavaScript in another user’s browser. Profile and registration fields, including the user’s name, accepted HTML and later rendered stored values as markup; the patch adds a BeautifulSoup-based validator that rejects fields containing HTML. Exploitation requires another user to view the stored value, allowing script execution in the docassemble origin with bounded confidentiality and integrity impact.
Summary
What happened
Stored XSS in JHPyle docassemble before 1.4.97 allows remote attackers to execute JavaScript in another user’s browser. Profile and registration fields, including the user’s name, accepted HTML and later rendered stored values as markup; the patch adds a BeautifulSoup-based validator that rejects fields containing HTML. Exploitation requires another user to view the stored value, allowing script execution in the docassemble origin with bounded confidentiality and integrity impact.
The record
- CVE
- CVE-2024-27290
- Published
- Feb 29, 2024
- Updated
- Aug 5, 2024
- Vendor
- JHPyle
- Product
- docassemble
- Classifications
- CWE-79, CAPEC-592, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 29, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=< 1.4.97
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