CVE-2025-5164 PerfreeBlog JWT JwtUtil hard-coded key

Medium 6.3 Published Updated

PerfreeBlog uses a hard-coded JWT key, allowing attackers to potentially bypass authentication or forge tokens.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2025-5164?

CVE-2025-5164 is a medium-severity vulnerability in PerfreeBlog, published on 26 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

A vulnerability has been found in PerfreeBlog 4.0.11 and classified as problematic. This vulnerability affects the function JwtUtil of the component JWT Handler. The manipulation leads to use of hard-coded cryptographic key . The attack can be initiated remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-798, CWE-321, CWE-320

Which versions are affected by CVE-2025-5164?

It affects 1 product.

Products include Perfree Perfreeblog.

How do I fix CVE-2025-5164?

No fix has been published for CVE-2025-5164 yet. Limit exposure of the affected software until one is available.

Is CVE-2025-5164 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5164 exists.

Sources

Also known as GHSA-q22v-8f6w-43w8.

Is CVE-2025-5164 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free