CVE-2025-9430
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-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 testing the /admin/options/update endpoint for stored cross-site scripting (XSS) by submitting malicious scripts in input parameters and observing if they are stored and executed on pages such as the homepage or /admin/options/index. Since the attack requires authentication, testing should be done with valid admin credentials. Specific commands are not provided in the resources, but manual testing or using web vulnerability scanners targeting stored XSS on the mentioned endpoint is recommended. [1, 2]
Can you explain this vulnerability to me?
CVE-2025-9430 is a stored Cross-Site Scripting (XSS) vulnerability in mtons mblog versions up to 3.5.0, specifically in the /admin/options/update endpoint. The vulnerability occurs because user-controlled input parameters are not properly validated or sanitized before being stored and displayed on various pages, including the frontend and admin panel. This allows attackers to inject malicious JavaScript code that executes when affected pages are loaded, potentially compromising data integrity and user security. Exploitation requires authentication and user interaction. [1, 2]
How can this vulnerability impact me? :
This vulnerability can allow attackers to inject and execute arbitrary JavaScript code in the context of users visiting the affected site pages. This can lead to session hijacking, defacement, or other malicious activities that compromise user data and site integrity. Since the malicious scripts are stored persistently, every user who accesses the affected pages may be exposed to the attack. The attack can be launched remotely but requires some authentication and user interaction. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
No known countermeasures or mitigations have been identified for this vulnerability. It is suggested to consider replacing the affected product or applying strict input validation and output encoding on the /admin/options/update endpoint to prevent stored XSS. Immediate steps include restricting access to the vulnerable endpoint, monitoring for suspicious activity, and avoiding use of affected versions (3.0 through 3.5.0) of mblog until a fix is available. [1, 2]