Contributor-level stored XSS via unsanitized page input
Published Mar 31, 2024 · Updated Aug 2, 2024
Stored XSS in iFlyChat – WordPress Chat 4.7.2 and earlier allows remote authenticated users to inject scripts into pages. Published sources do not identify the vulnerable parameter, handler, or storage path; they establish only insufficient input sanitization and output escaping. Contributor-level access is required to store the payload, and a later page view executes it in another user's browser.
Summary
What happened
Stored XSS in iFlyChat – WordPress Chat 4.7.2 and earlier allows remote authenticated users to inject scripts into pages. Published sources do not identify the vulnerable parameter, handler, or storage path; they establish only insufficient input sanitization and output escaping. Contributor-level access is required to store the payload, and a later page view executes it in another user's browser.
The record
- CVE
- CVE-2024-31108
- Published
- Mar 31, 2024
- Updated
- Aug 2, 2024
- Vendor
- iFlyChat
- Product
- iFlyChat – WordPress Chat
- Classifications
- CWE-79, CAPEC-592, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 31, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=n/a <=4.7.2
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