CVE-2025-10245
BaseFortify
Publication date: 2025-09-11
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 |
|---|---|---|
| display_paineis | tga | 7.1.41 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability impact me? :
This vulnerability can impact confidentiality, integrity, and availability of the affected system. An attacker with sufficient privileges can rename or move directories arbitrarily outside the intended folder, potentially deleting, overwriting, or disclosing sensitive files. This can lead to data corruption, unauthorized data access, or disruption of system operations. [1, 3]
Can you explain this vulnerability to me?
CVE-2025-10245 is a path traversal vulnerability in Display Painéis TGA up to version 7.1.41, specifically in the Galeria Page component at the /gallery/rename endpoint. It occurs because the application improperly handles the 'current_folder' argument, allowing an attacker to manipulate directory paths to traverse outside the intended restricted directory. This enables unauthorized renaming or moving of files and folders outside the application's allowed scope, potentially leading to unauthorized access or modification of files. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /gallery/rename endpoint for path traversal attempts using directory traversal sequences such as "../" in the current_folder argument. For example, you can attempt to rename a folder within the gallery to a path outside the intended directory, such as renaming "/gallery/POC2" to "../POCtest" and observe if the folder moves outside the application directory. Commands or scripts that send HTTP requests to the /gallery/rename endpoint with manipulated current_folder parameters containing "../" sequences can help detect the vulnerability. Monitoring for unexpected directory changes or unauthorized file movements in the gallery directory can also indicate exploitation attempts. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include validating all user-supplied paths before processing file operations to ensure they do not contain path traversal sequences such as "../". Restrict file management actions strictly to the application's base directory by implementing access control rules. Use safe APIs like realpath() and basename() to normalize and reject malicious input. Since no vendor patch or official mitigation is available, consider replacing the affected product with an alternative. Monitoring and restricting access to the file management panel to trusted users with minimal privileges can also reduce risk. [1, 3]