Unauthenticated stored script execution via address input
Published Apr 24, 2025 · Updated Apr 8, 2026
Stored XSS in WPQuark eForm - WordPress Form Builder 4.18.0 and earlier allows remote attackers to execute scripts via form input. The address element accepts untrusted form input without sufficient sanitization and later renders it without adequate output escaping. No account is required; the stored script runs when a visitor accesses the injected page and can act within that site's browser origin.
Summary
What happened
Stored XSS in WPQuark eForm - WordPress Form Builder 4.18.0 and earlier allows remote attackers to execute scripts via form input. The address element accepts untrusted form input without sufficient sanitization and later renders it without adequate output escaping. No account is required; the stored script runs when a visitor accesses the injected page and can act within that site's browser origin.
The record
- CVE
- CVE-2025-1294
- Published
- Apr 24, 2025
- Updated
- Apr 8, 2026
- Vendor
- WPQuark
- Product
- eForm - WordPress Form Builder
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 24, 2025CVE 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 <=4.18.0
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