Stored script execution through map block
Published Sep 17, 2024 · Updated Apr 28, 2026
Stored XSS in the map block of WPSoul Greenshift 9.3.7 and earlier allows remote authenticated users to execute script in visitors' browsers. The 9.4 changelog identifies the map block as the affected locus, but the public advisory does not identify the unsanitized field or output operation. Contributor access is required to store the payload, and a privileged user must view the affected content before the script runs in that user's browser.
Summary
What happened
Stored XSS in the map block of WPSoul Greenshift 9.3.7 and earlier allows remote authenticated users to execute script in visitors' browsers. The 9.4 changelog identifies the map block as the affected locus, but the public advisory does not identify the unsanitized field or output operation. Contributor access is required to store the payload, and a privileged user must view the affected content before the script runs in that user's browser.
The record
- CVE
- CVE-2024-44005
- Published
- Sep 17, 2024
- Updated
- Apr 28, 2026
- Vendor
- WPSoul
- Product
- Greenshift
- Classifications
- CWE-79, CAPEC-592, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 17, 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=0 <=9.3.7 changes=[{"at":"9.4","status":"unaffected"}]
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