Full-path disclosure via verbose error output
Published Jan 24, 2025 · Updated May 11, 2026
Full-path disclosure in Paytium 4.4.11 and earlier allows remote attackers to read the server installation path through error output. The public advisory does not identify the affected file or request, but states that the plugin exposes a full folder or file path when it generates an error. No authentication or user interaction is required, and the reported consequence is limited to disclosure that can assist later attacks.
Summary
What happened
Full-path disclosure in Paytium 4.4.11 and earlier allows remote attackers to read the server installation path through error output. The public advisory does not identify the affected file or request, but states that the plugin exposes a full folder or file path when it generates an error. No authentication or user interaction is required, and the reported consequence is limited to disclosure that can assist later attacks.
The record
- CVE
- CVE-2025-24552
- Published
- Jan 24, 2025
- Updated
- May 11, 2026
- Vendor
- Paytium
- Product
- Paytium
- Classifications
- CWE-209, CAPEC-37
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 24, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record 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=0 <=4.4.11 changes=[{"at":"4.4.12","status":"unaffected"}]
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
No public exploit references are available in this record.
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