Unauthorized file disclosure via unchecked src path
Published Feb 18, 2025 · Updated Feb 19, 2025
Path traversal in WeGIA before 3.2.14 allows remote attackers to read sensitive server files through the examples.php endpoint. The examples.php endpoint insufficiently validates the POST src parameter, so ../ sequences escape the intended directory and resolve arbitrary local paths. No authentication or user interaction is required; disclosure includes config.php database credentials and other readable host files.
Summary
What happened
Path traversal in WeGIA before 3.2.14 allows remote attackers to read sensitive server files through the examples.php endpoint. The examples.php endpoint insufficiently validates the POST src parameter, so ../ sequences escape the intended directory and resolve arbitrary local paths. No authentication or user interaction is required; disclosure includes config.php database credentials and other readable host files.
The record
- CVE
- CVE-2025-26615
- Published
- Feb 18, 2025
- Updated
- Feb 19, 2025
- Vendor
- LabReDeS - Laboratório de Redes, Desenvolvimento e Segurança
- Product
- WeGIA
- Classifications
- CWE-22, CWE-284, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 18, 2025CVE publishedPublication date reported by the CVE source.
- Feb 19, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.2.14
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Vendor advisory curl file-read proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo