Stored XSS via unescaped testimonial link field
Published Apr 24, 2024 · Updated Aug 1, 2024
Stored XSS in WPChill Strong Testimonials before 3.1.12 allows remote authenticated users to inject scripts through the Full Name field. A URL-style testimonial view emits the stored Full Name value into link markup without adequate validation or output escaping, so a quote can introduce an event handler. Contributor access and approval of the testimonial are required, unless an Author publishes it; the script runs when a visitor opens the affected view and interacts with the link.
Summary
What happened
Stored XSS in WPChill Strong Testimonials before 3.1.12 allows remote authenticated users to inject scripts through the Full Name field. A URL-style testimonial view emits the stored Full Name value into link markup without adequate validation or output escaping, so a quote can introduce an event handler. Contributor access and approval of the testimonial are required, unless an Author publishes it; the script runs when a visitor opens the affected view and interacts with the link.
The record
- CVE
- CVE-2024-3261
- Published
- Apr 24, 2024
- Updated
- Aug 1, 2024
- Vendor
- WPChill
- Product
- Strong Testimonials
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 24, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 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=0 <3.1.12
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
- WPScan Full Name field proof of conceptproof of concept · demonstrated
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