CVE-2025-14722
Remote Cross-Site Scripting in vion707 DMadmin Backend Add Function
Publication date: 2025-12-15
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 |
|---|---|---|
| vion707 | dmadmin | * |
| thinkphp | thinkphp | 3.23 |
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
Can you explain this vulnerability to me?
CVE-2025-14722 is a stored Cross-Site Scripting (XSS) vulnerability in the vion707 DMadmin software, specifically in the Add function of the Backend's AddonsController.class.php file. It occurs because user input is not properly sanitized or escaped before being stored and later displayed in the backend interface. This allows an authenticated attacker to inject malicious scripts that execute when the stored data is viewed, potentially compromising the integrity of the application. The attack requires authentication and some user interaction, and a proof-of-concept exploit is publicly available. [2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing an authenticated attacker to execute malicious scripts within the backend interface of the DMadmin software. This can compromise the integrity of the system by manipulating or hijacking user sessions, stealing sensitive information, or performing unauthorized actions within the application. Since the exploit is remotely executable and publicly disclosed, it poses a risk if the affected software is in use and not mitigated. [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by searching for the vulnerable file path or by testing the Add function in the Admin/Controller/AddonsController.class.php for improper input sanitization leading to XSS. Google dorking can be used to identify exposed instances by searching for the vulnerable file path. Additionally, testing input fields in the backend for stored XSS payloads can help detect the issue. Specific commands are not provided, but using web vulnerability scanners targeting XSS or manual testing with XSS payloads in the affected parameters is suggested. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing or updating the affected component or product since no known mitigations or countermeasures have been published. Avoid using the vulnerable version of vion707 DMadmin and restrict access to the backend interface to trusted users only. Implement input validation and output encoding as a general best practice to reduce XSS risks until a patch or update is available. [2]