Cyber Resilience

CVE-2025-60355

Zhyd Oneblog ≤ 2.3.9

Public PoC
Published
28 October 2025
Modified
04 March 2026
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0046 38th percentile
Risk Priority 71 floored blend · peak EPSS

Summary

CVE-2025-60355 is a critical-severity Improper Neutralization of Special Elements Used in a Template Engine (CWE-1336) vulnerability in Zhyd Oneblog. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Template Injection (T1221); ranked at the 38th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-60355 is a Server-Side Template Injection (SSTI) vulnerability in zhangyd-c OneBlog versions 2.3.9 and prior, exploitable through FreeMarker templates. Mapped to CWE-1336, it carries a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), reflecting critical severity due to its potential for complete system compromise.

Unauthenticated attackers with network access can exploit this vulnerability remotely with low complexity and no user interaction required. Exploitation enables high-impact disruption to confidentiality, integrity, and availability, allowing attackers to inject malicious templates that may lead to arbitrary code execution on the affected server.

Mitigation details are available in the referenced advisory at https://github.com/line2222/vuln/issues/4.

EU & UK References

Vulnerability Data

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

CWE(s)
CWE-1336

Related Threats

MITRE ATT&CK Enterprise Techniques

T1221 Template Injection Stealth
Adversaries may create or modify references in user document templates to conceal malicious code or force authentication attempts.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-54954Same product: Zhyd Oneblog
CVE-2024-29472Same product: Zhyd Oneblog
CVE-2024-29473Same product: Zhyd Oneblog
CVE-2025-2835Same product: Zhyd Oneblog
CVE-2024-29470Same product: Zhyd Oneblog
CVE-2025-2833Same product: Zhyd Oneblog
CVE-2025-56264Same product: Zhyd Oneblog
CVE-2024-29471Same product: Zhyd Oneblog
CVE-2024-29474Same product: Zhyd Oneblog
CVE-2024-29469Same product: Zhyd Oneblog

Affected Assets

zhyd
oneblog
≤ 2.3.9

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.3.2
  • V1.3.7
  • V1.3.10

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and static analysis can discover missing neutralization of template directives.

SI-10 Information Input Validation good match

Input validation rejects or sanitizes untrusted data before it reaches the template engine, stopping injection of special syntax.

SA-8 Security and Privacy Engineering Principles partial match

Security engineering principles require use of safe templating APIs and proper escaping of external input.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper input neutralization in template engines to prevent injection.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect template-injection flaws but does not itself implement neutralization controls.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and sanitization that directly prevents template-injection weaknesses.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for neutralizing special elements in template engines.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce the likelihood of unsafe template processing but do not prescribe specific neutralization techniques.

A.8.28 Secure coding partial match
prevents

Secure coding standards require proper escaping or sandboxing of template directives, directly mitigating CWE-1336.

References