CVE-2025-14013
BaseFortify
Publication date: 2025-12-04
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| jizhicms | jizhicms | to 2.5.5 (inc) |
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. |
| CWE-94 | The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by identifying instances of JIZHICMS up to version 2.5.5 running the vulnerable Comment Handler component. One method is to use Google dorking with the query `inurl:index.php/admins/Comment/addcomment.html` to find potentially vulnerable targets. Additionally, monitoring HTTP requests for suspicious or malicious payloads in the `body` parameter of POST requests to `/index.php/admins/Comment/addcomment.html` can help detect exploitation attempts. Specific commands are not provided, but using web vulnerability scanners or custom scripts to test for stored XSS by injecting payloads into the `body` parameter and observing if they are executed when comments are viewed can be effective. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing or upgrading the affected product to a version that is not vulnerable, if available. Since no vendor response or patch is reported, applying input validation and output encoding on the `body` parameter in the Comment Handler component can help prevent XSS attacks. Restricting access to the vulnerable admin comment feature and monitoring for suspicious activity are also recommended. Ultimately, removing or disabling the vulnerable functionality until a fix is available is advised. [2]
Can you explain this vulnerability to me?
This vulnerability exists in JIZHICMS up to version 2.5.5, specifically in the Comment Handler component within the file /index.php/admins/Comment/addcomment.html. It involves the manipulation of the 'body' argument, which leads to a cross-site scripting (XSS) vulnerability. This means an attacker can inject malicious scripts that may be executed in the context of a user's browser. The attack can be initiated remotely, and an exploit is publicly available.
How can this vulnerability impact me? :
The vulnerability can allow an attacker to perform cross-site scripting attacks by injecting malicious scripts through the 'body' argument in the comment functionality. This can lead to unauthorized actions performed on behalf of users, potential session hijacking, or other malicious activities executed in the user's browser. However, the CVSS scores indicate a relatively low severity with limited impact on confidentiality and availability, but some impact on integrity.