{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5164 exists.","fix":"No fix has been published for CVE-2025-5164 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2025-5164 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5164 exists.\n\nAffected product: PerfreeBlog. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-5164/ (Markdown: https://insights.sbomify.com/CVE-2025-5164/index.md)","id":"CVE-2025-5164","markdown":"https://insights.sbomify.com/CVE-2025-5164/index.md","name":"CVE-2025-5164","record":{"aliases":["GHSA-q22v-8f6w-43w8"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"PerfreeBlog","requires_auth":"none","summary":"PerfreeBlog uses a hard-coded JWT key, allowing attackers to potentially bypass authentication or forge tokens.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"perfreeblog","vendor":"perfree"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"},{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"},{"id":"CWE-320","name":null}],"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\r . 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"PerfreeBlog JWT JwtUtil hard-coded key","id":"CVE-2025-5164","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Open Asset Import Library Assimp MDCLoader.cpp ValidateSurfaceHeader out-of-bounds","id":"CVE-2025-5165"},"packages":[],"prev":{"headline":"yangshare 技术杨工 warehouseManager 仓库管理系统 access control","id":"CVE-2025-5163"},"products":["PerfreeBlog"],"published":"2025-05-26","related":[{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2023-30333","kev_date_added":null,"published":"2023-05-18"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2023-27757","kev_date_added":null,"published":"2023-03-15"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2025-29281","kev_date_added":null,"published":"2025-04-15"},{"cvss_score":7.6,"headline":"Path traversal in n/a","id":"CVE-2025-60730","kev_date_added":null,"published":"2025-10-24"},{"cvss_score":7.6,"headline":"File upload in n/a","id":"CVE-2025-60731","kev_date_added":null,"published":"2025-10-24"},{"cvss_score":7.6,"headline":"File upload in n/a","id":"CVE-2025-60735","kev_date_added":null,"published":"2025-10-24"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2025-29420","kev_date_added":null,"published":"2025-08-25"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-28","vendors":["n/a"]},"summary":"PerfreeBlog uses a hard-coded JWT key, allowing attackers to potentially bypass authentication or forge tokens.","url":"https://insights.sbomify.com/CVE-2025-5164/"}