CVE-2025-60735 File upload in n/a
High 7.6
Published
Updated
Check this codebase for CVE-2025-60735 and fix it if it is affected.
What it is: CVE-2025-60735 is a high-severity vulnerability in n/a, published on 24 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-60735 exists.
Affected product: n/a. 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-60735/ (Markdown: https://insights.sbomify.com/CVE-2025-60735/index.md)
Attackers can upload malicious files via the installPlugin function in PerfreeBlog, potentially leading to remote code execution.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-60735?
CVE-2025-60735 is a high-severity vulnerability in n/a, published on 24 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
PerfreeBlog v4.0.11 has a File Upload vulnerability in the installPlugin function
Weakness: CWE-434
Which versions are affected by CVE-2025-60735?
It affects 1 product.
Products include Perfree Perfreeblog.
How do I fix CVE-2025-60735?
No fix has been published for CVE-2025-60735 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-60735 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-60735 exists.
Other vulnerabilities in n/a
Sources
Also known as GHSA-5992-r8wx-j2j7.