CVE-2024-54954
Zhyd Oneblog ≤ 2.3.6
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2024-54954 is a high-severity Improper Neutralization of Special Elements Used in a Template Engine (CWE-1336) vulnerability in Zhyd Oneblog. Its CVSS base score is 8.0 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Template Injection (T1221); ranked at the 36th 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-2024-54954 is a template injection vulnerability affecting OneBlog version 2.3.6, specifically in the template management department. This flaw, classified under CWE-1336, allows improper handling of user-supplied input in templates, enabling malicious code execution within the templating engine. The vulnerability received a CVSS v3.1 base score of 8.0, reflecting its high severity due to network accessibility and significant impact potential.
An attacker with low privileges (PR:L), such as an authenticated user, can exploit this over the network (AV:N) with low complexity (AC:L), though it requires user interaction (UI:R), like clicking a malicious link or input. Successful exploitation grants high confidentiality (C:H), integrity (I:H), and availability (A:H) impacts without changing scope (S:U), potentially leading to full server compromise, data exfiltration, or arbitrary code execution on the affected OneBlog instance.
Advisories and additional details, including potential patches or workarounds, are documented in references such as the GitHub Gist at https://gist.github.com/kaoniniang2/03658cc78e789b992b378f4951bedfb7 and the Gitee issue tracker at https://gitee.com/yadong.zhang/DBlog/issues/IB6552. Security practitioners should review these for version-specific mitigation guidance.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-52716
Vulnerability Data
OneBlog v2.3.6 was discovered to contain a template injection vulnerability via the template management department.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.3.2V1.3.7V1.3.10
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and static analysis can discover missing neutralization of template directives.
Input validation rejects or sanitizes untrusted data before it reaches the template engine, stopping injection of special syntax.
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.
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.
Security testing can detect template-injection flaws but does not itself implement neutralization controls.
Secure development life cycle mandates input validation and sanitization that directly prevents template-injection weaknesses.
Application security requirements explicitly call for neutralizing special elements in template engines.
Secure architecture principles reduce the likelihood of unsafe template processing but do not prescribe specific neutralization techniques.
Secure coding standards require proper escaping or sandboxing of template directives, directly mitigating CWE-1336.