Unauthenticated stored XSS via unsanitized page input
Published May 13, 2024 · Updated Apr 28, 2026
Stored XSS in Propovoice CRM 1.7.6.2 and earlier allows remote attackers to inject scripts that execute when a user opens an affected page. The plugin stores page input without sufficient sanitization and later renders it without adequate output escaping; public records do not identify the affected field or rendering path. No authentication is required to plant the payload, but a user must access the injected page, where the script runs in the user's browser context.
Summary
What happened
Stored XSS in Propovoice CRM 1.7.6.2 and earlier allows remote attackers to inject scripts that execute when a user opens an affected page. The plugin stores page input without sufficient sanitization and later renders it without adequate output escaping; public records do not identify the affected field or rendering path. No authentication is required to plant the payload, but a user must access the injected page, where the script runs in the user's browser context.
The record
- CVE
- CVE-2024-4747
- Published
- May 13, 2024
- Updated
- Apr 28, 2026
- Vendor
- Propovoice
- Product
- Propovoice CRM
- Classifications
- CWE-79, CAPEC-592, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 13, 2024CVE publishedPublication date reported by the CVE source.
- Apr 28, 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=n/a <=1.7.6.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