CVE-2023-53927
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 |
|---|---|---|
| phpjabbers | simple_cms | 5.0 |
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 PHPJabbers Simple CMS 5.0. Authenticated attackers can inject malicious scripts into section name parameters. These scripts are stored and later executed when administrators view the affected sections, allowing client-side code execution.
How can this vulnerability impact me? :
The vulnerability can allow attackers to execute malicious client-side scripts in the context of the administrator's browser. This can lead to unauthorized actions, data theft, session hijacking, or other malicious activities performed with the administrator's privileges.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by attempting to create a section with a malicious payload in the section name parameter and observing if the payload executes when the section is viewed. A proof-of-concept involves sending a crafted POST request to the endpoint `/simplecms/index.php?controller=pjAdminSections&action=pjActionCreate` with a payload such as `"><img src=x onerror=alert(\"Stored\")>` in the section name field. Monitoring HTTP requests to this endpoint and checking for such payloads can help detect exploitation attempts. For example, using curl to send a test payload: `curl -X POST -d 'section_name="><img src=x onerror=alert(\"Stored\")>' https://your-simplecms-site/simplecms/index.php?controller=pjAdminSections&action=pjActionCreate` can verify if the vulnerability exists. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the admin panel to trusted users only, ensuring that only authenticated and authorized users can create or modify sections. Additionally, applying input validation and output encoding on the section name parameter to prevent script injection is critical. If a patch or update is available from the vendor, it should be applied promptly. As a temporary measure, monitoring and blocking suspicious POST requests to the section creation endpoint can reduce exploitation risk. [1, 3]