Unauthenticated sensitive data disclosure
Published Dec 31, 2025 · Updated Dec 31, 2025
Sensitive information exposure in Vladimir Statsenko Terms descriptions 3.4.10 and earlier allows remote attackers to read embedded sensitive data. Patchstack has not published the affected code locus, the sensitive fields disclosed, or the operation that inserts them into a response. The network path requires no authentication or user interaction, and the documented consequence is limited to confidentiality loss.
Summary
What happened
Sensitive information exposure in Vladimir Statsenko Terms descriptions 3.4.10 and earlier allows remote attackers to read embedded sensitive data. Patchstack has not published the affected code locus, the sensitive fields disclosed, or the operation that inserts them into a response. The network path requires no authentication or user interaction, and the documented consequence is limited to confidentiality loss.
The record
- CVE
- CVE-2025-62139
- Published
- Dec 31, 2025
- Updated
- Dec 31, 2025
- Vendor
- Vladimir Statsenko
- Product
- Terms descriptions
- Classifications
- CWE-201, CAPEC-37, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 31, 2025CVE publishedPublication date reported by the CVE source.
- Dec 31, 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=n/a <=3.4.9
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