Stored XSS via unescaped legacy shortcode attributes
Published May 18, 2024 · Updated Apr 8, 2026
Stored XSS in GiveWP 3.10.0 and earlier allows remote authenticated users to inject scripts through legacy give_form shortcode attributes. The Give_Donate_Form shortcode path accepts user-supplied attributes without sufficient sanitization and emits them without adequate output escaping. Contributor-level access and a legacy form are required; the stored script runs when a visitor opens the injected page.
Summary
What happened
Stored XSS in GiveWP 3.10.0 and earlier allows remote authenticated users to inject scripts through legacy give_form shortcode attributes. The Give_Donate_Form shortcode path accepts user-supplied attributes without sufficient sanitization and emits them without adequate output escaping. Contributor-level access and a legacy form are required; the stored script runs when a visitor opens the injected page.
The record
- CVE
- CVE-2024-3714
- Published
- May 18, 2024
- Updated
- Apr 8, 2026
- Vendor
- Liquid Web
- Product
- GiveWP
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 18, 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 <=3.10.0
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