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

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

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 May 2025
- **Updated:** 28 May 2025
- **Also known as:** GHSA-q22v-8f6w-43w8

## 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 (Use of Hard-coded Credentials), CWE-321 (Use of Hard-coded Cryptographic Key), CWE-320

## Which versions are affected by CVE-2025-5164?

It affects 1 product.


Products: 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.

## Other vulnerabilities in PerfreeBlog

- [CVE-2023-30333](https://insights.sbomify.com/CVE-2023-30333/): File upload in n/a (critical 9.8)
- [CVE-2023-27757](https://insights.sbomify.com/CVE-2023-27757/): File upload in n/a (critical 9.8)
- [CVE-2025-29281](https://insights.sbomify.com/CVE-2025-29281/): File upload in n/a (high 8.8)
- [CVE-2025-60730](https://insights.sbomify.com/CVE-2025-60730/): Path traversal in n/a (high 7.6)
- [CVE-2025-60731](https://insights.sbomify.com/CVE-2025-60731/): File upload in n/a (high 7.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-5164 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5164 exists.

Affected product: PerfreeBlog. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-5164/ (Markdown: https://insights.sbomify.com/CVE-2025-5164/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-5164
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-5164
- OSV: https://osv.dev/vulnerability/CVE-2025-5164

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-5164/
Summaries are generated and may contain mistakes; the official description above is the record.