Unauthenticated stored XSS via unsanitized Referer header
Published Mar 12, 2024 · Updated Apr 8, 2026
Stored XSS in BoldGrid weForms 1.6.21 and earlier allows remote attackers to inject scripts through a crafted Referer header. Form-submission handling stores the unsanitized header in entry and notification data, and affected views render it without output escaping. No authentication is required to submit the header; the script runs when a user opens the poisoned entry or notification view, enabling actions in that user's browser context.
Summary
What happened
Stored XSS in BoldGrid weForms 1.6.21 and earlier allows remote attackers to inject scripts through a crafted Referer header. Form-submission handling stores the unsanitized header in entry and notification data, and affected views render it without output escaping. No authentication is required to submit the header; the script runs when a user opens the poisoned entry or notification view, enabling actions in that user's browser context.
The record
- CVE
- CVE-2024-0386
- Published
- Mar 12, 2024
- Updated
- Apr 8, 2026
- Vendor
- Web Ventures
- Product
- weForms
- Classifications
- CWE-79, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 12, 2024CVE publishedPublication date reported by the CVE source.
- Apr 8, 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=0 <=1.6.21
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