CVE-2023-53910
BaseFortify
Publication date: 2025-12-17
Last updated on: 2025-12-27
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wbce | wbce_cms | 1.6.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a stored cross-site scripting (XSS) issue in WBCE CMS 1.6.1. Authenticated attackers can inject malicious JavaScript code by inserting script tags into page content using the WYSIWYG editor. They do this by sending POST requests to /wbce/modules/wysiwyg/save.php with malicious script content in the content parameter. When other users view the affected page, the injected JavaScript executes in their browsers.
How can this vulnerability impact me? :
The vulnerability can allow attackers to execute arbitrary JavaScript in the context of the affected website for users who view the compromised pages. This can lead to theft of user credentials, session hijacking, defacement, or distribution of malware, potentially compromising user data and site integrity.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for POST requests to the endpoint /wbce/modules/wysiwyg/save.php containing suspicious script tags in the content parameter. You can use network traffic inspection tools or web server logs to identify such requests. For example, using grep on web server logs: grep -i 'POST /wbce/modules/wysiwyg/save.php' /path/to/access.log | grep '<script>'. Additionally, tools like Wireshark or intrusion detection systems can be configured to alert on such patterns. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the WYSIWYG editor to trusted users only, applying input validation or sanitization to prevent script tags from being saved in page content, and monitoring or blocking suspicious POST requests to /wbce/modules/wysiwyg/save.php. If possible, update or patch WBCE CMS to a version where this vulnerability is fixed. Until a patch is available, consider disabling the WYSIWYG editor or limiting its functionality to prevent script injection. [1]