CVE-2025-9433
BaseFortify
Publication date: 2025-08-26
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 |
|---|---|---|
| mtons | mblog | to 3.5.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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 reflected Cross-Site Scripting (XSS) issue in the mtons mblog application (version 3.5.0 and earlier). It occurs in the admin panel's /admin/user/list endpoint, specifically in the 'name' parameter used for searching users. The parameter does not have proper validation or sanitization, allowing attackers to inject malicious scripts that are reflected back in the response. This enables attackers to execute arbitrary scripts in the context of the admin panel. [1, 2]
How can this vulnerability impact me? :
An attacker exploiting this vulnerability can execute arbitrary JavaScript in the context of the admin panel. This can lead to session hijacking, theft of sensitive information, unauthorized actions performed on behalf of the admin user, or other malicious activities within the admin interface. Since the attack can be initiated remotely, it poses a significant security risk to the affected system. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by sending crafted HTTP requests to the /admin/user/list endpoint with a malicious payload in the 'name' parameter and observing if the payload is reflected unescaped in the response. For example, you can use curl to test the vulnerability with the following command: curl -i "http://<target-host>/admin/user/list?pageNo=1&name=1\"><img src=1 onerror=alert(/username/)>" If the response contains the injected <img> tag and triggers a script execution (e.g., an alert), the vulnerability is present. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the /admin/user/list endpoint to trusted users only, such as by implementing strong authentication and IP whitelisting. Additionally, avoid using the vulnerable version of mblog (up to 3.5.0) and apply any available patches or updates from the vendor. As a temporary workaround, input validation and output encoding should be implemented on the 'name' parameter to prevent script injection. [1, 2]