Stored XSS via unneutralized settings fields
Published Apr 17, 2024 · Updated Mar 21, 2025
Stored XSS in PESCMS-TEAM 2.3.6 allows remote authenticated users to execute scripts in visitors' browsers through saved settings. The settings action stores payloads entered in the domain and other fields without neutralizing HTML, then renders them on later visits. Execution requires an account to save a payload and a visitor to reopen the affected page; the demonstrated consequence is persistent script execution.
Summary
What happened
Stored XSS in PESCMS-TEAM 2.3.6 allows remote authenticated users to execute scripts in visitors' browsers through saved settings. The settings action stores payloads entered in the domain and other fields without neutralizing HTML, then renders them on later visits. Execution requires an account to save a payload and a visitor to reopen the affected page; the demonstrated consequence is persistent script execution.
The record
- CVE
- CVE-2024-30952
- Published
- Apr 17, 2024
- Updated
- Mar 21, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 17, 2024CVE publishedPublication date reported by the CVE source.
- Mar 21, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Stored XSS in PESCMS-TEAM 2.3.6 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