JWT information disclosure via hard-coded key
Published May 26, 2025 · Updated May 28, 2025
Hard-coded key use in Perfree PerfreeBlog 4.0.11 allows remote attackers to expose limited JWT information through JwtUtil. JwtUtil supplies fixed cryptographic material to the JWT handler instead of using a deployment-specific secret. Exploitation requires a high-complexity remote attack, and the published vectors limit the demonstrated consequence to confidentiality loss without integrity or availability impact.
Summary
What happened
Hard-coded key use in Perfree PerfreeBlog 4.0.11 allows remote attackers to expose limited JWT information through JwtUtil. JwtUtil supplies fixed cryptographic material to the JWT handler instead of using a deployment-specific secret. Exploitation requires a high-complexity remote attack, and the published vectors limit the demonstrated consequence to confidentiality loss without integrity or availability impact.
The record
- CVE
- CVE-2025-5164
- Published
- May 26, 2025
- Updated
- May 28, 2025
- Vendor
- Perfree
- Product
- PerfreeBlog
- Classifications
- CWE-321, CWE-320
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 26, 2025CVE publishedPublication date reported by the CVE source.
- May 28, 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=4.0.11
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.
Public exploit references
- PerfreeBlog 4.0.11 hard-coded key proof of conceptproof of concept · unverified
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