Stored XSS via unescaped autofilled display names
Published Apr 27, 2024 · Updated Apr 8, 2026
Stored XSS in Form Maker by 10Web 1.15.24 and earlier allows remote authenticated users to inject scripts through a display name. The Name field's autofill path copies the current WordPress user's stored display name into rendered form markup without sufficient sanitization or contextual output escaping. Subscriber-level access is sufficient to plant the value, while script execution requires a browser to render a form that autofills the crafted display name.
Summary
What happened
Stored XSS in Form Maker by 10Web 1.15.24 and earlier allows remote authenticated users to inject scripts through a display name. The Name field's autofill path copies the current WordPress user's stored display name into rendered form markup without sufficient sanitization or contextual output escaping. Subscriber-level access is sufficient to plant the value, while script execution requires a browser to render a form that autofills the crafted display name.
The record
- CVE
- CVE-2024-2258
- Published
- Apr 27, 2024
- Updated
- Apr 8, 2026
- Vendor
- 10Web
- Product
- Form Maker by 10Web
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 27, 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=- <=1.15.24
What conditions does exploitation require?
What is affected?
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