Quick answers
- Is CVE-2025-60729 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-60729 being exploited in the wild.
- How severe is CVE-2025-60729?
- Medium severity, with a CVSS score of 5.3, published 24 October 2025.
- Which products and versions are affected?
- Perfreeblog 4.0.11.
- Is there a fix for CVE-2025-60729?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2025-60729 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2025-60729?
- Check whether you run Perfreeblog at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An arbitrary file read vulnerability exists in PerfreeBlog v4.0.11 within the `validThemeFilePath` function. The vulnerability arises because the path validation logic only checks if the requested path contains the `themePath` string, failing to prevent directory traversal sequences like `../`. Furthermore, the `/api/auth/theme/getThemeFileContent` endpoint lacks proper authorization checks (missing `hasPermission` validation), allowing any registered user—or an unauthenticated user in some configurations—to submit a crafted POST request. Attackers can leverage this to read sensitive system files such as `application-prod.yaml` or `/etc/passwd` by manipulating the `themePath` and `path` parameters.
Affected products
- Perfree PerfreeBlog 4.0.11
Timeline
- 2025-10-24: advisory: NVD published the vulnerability report.