Cross-site scripting via unsanitized name parameter
Published Nov 11, 2022 · Updated Apr 15, 2025
Cross-site scripting in ForU CMS allows remote authenticated users to execute script in another user's browser via cms_chip.php. The cms_chip.php handler incorporates the name parameter into generated page content without neutralizing browser-executable markup. A low-privilege account and user interaction are required, and public records do not identify affected versions or further code details.
Summary
What happened
Cross-site scripting in ForU CMS allows remote authenticated users to execute script in another user's browser via cms_chip.php. The cms_chip.php handler incorporates the name parameter into generated page content without neutralizing browser-executable markup. A low-privilege account and user interaction are required, and public records do not identify affected versions or further code details.
The record
- CVE
- CVE-2022-3943
- Published
- Nov 11, 2022
- Updated
- Apr 15, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, CWE-707, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 11, 2022CVE publishedPublication date reported by the CVE source.
- Apr 15, 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.
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
- ForU CMS cms_chip.php name-parameter XSS proof of conceptproof of concept · unverified
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