# CVE-2025-60355: Code injection in n/a

> Attackers can execute arbitrary code via Server-Side Template Injection in OneBlog's FreeMarker templates.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Oct 2025
- **Updated:** 4 Mar 2026
- **Also known as:** GHSA-q7cx-22m3-64gr

## What is CVE-2025-60355?

CVE-2025-60355 is a critical code injection vulnerability in n/a, published on 28 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

zhangyd-c OneBlog v2.3.9 and before was vulnerable to SSTI (Server-Side Template Injection) via FreeMarker templates.

Weakness: CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)

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

It affects 1 product.


Products: Zhyd Oneblog.

## How do I fix CVE-2025-60355?

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

## Is CVE-2025-60355 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-54954](https://insights.sbomify.com/CVE-2024-54954/): Code injection in n/a (high 8.0)
- [CVE-2025-56264](https://insights.sbomify.com/CVE-2025-56264/): Denial of service in n/a (high 7.5)
- [CVE-2025-2833](https://insights.sbomify.com/CVE-2025-2833/): zhangyd-c OneBlog HTTP Header redos (medium 6.9)
- [CVE-2022-34012](https://insights.sbomify.com/CVE-2022-34012/): Privilege escalation in n/a (medium 6.5)
- [CVE-2024-29469](https://insights.sbomify.com/CVE-2024-29469/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-60355 is a critical code injection vulnerability in n/a, published on 28 Oct 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-60355 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-60355/ (Markdown: https://insights.sbomify.com/CVE-2025-60355/index.md)
```

## Sources

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

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