CVE-2025-60355
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedzhangyd-c OneBlog v2.3.9 and before was vulnerable to SSTI (Server-Side Template Injection) via FreeMarker templates.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencezhangyd-c OneBlog v2.3.9 and earlier versions contain a Server-Side Template Injection (SSTI) vulnerability in the FreeMarker template engine. Attackers can inject malicious template directives through user input that gets directly rendered without sanitization, potentially achieving remote code execution on the server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.3.9CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed OneBlog versionLocate the version identifier in the application's build files (pom.xml, package.json), WAR file metadata, or the application'sAbout/Help page. Common locations include WEB-INF/build-info.properties or the admin dashboard.Affected if The installed version is 2.3.9 or any earlier version (e.g., 2.3.0, 2.2.x, etc.).
-
Locate FreeMarker template usageSearch the codebase for FreemarkerConfigurer, FreeMarkerConfig, or template engine initialization code. Look for .ftl files in the resources/templates directory and identify controllers/endpoints that return TemplateResponse or use TemplateLoader.Affected if FreeMarker is actively used as the template engine in the application.
-
Trace user input to template renderingIdentify all endpoints accepting user-submitted data (POST/GET parameters, request body). Review the code path from input receipt to template processing. Look for code that passes user input directly to template processing methods such as process(), render(), or StringTemplateLoader.Affected if User-controlled input flows directly into template rendering without intermediate processing.
-
Verify input sanitization or sandboxingInspect the template rendering code for the presence of input validation, sanitization functions, or FreeMarker's sandbox configuration (TemplateClassResolver, ObjectWrapper settings). Check if custom template loaders or security policies are defined.Affected if No input sanitization, validation, or FreeMarker sandboxing is implemented between user input and template rendering.
You are affected if your OneBlog version is 2.3.9 or earlier AND user input can reach FreeMarker template rendering without sanitization.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2.3.9
Upgrade OneBlog to a version beyond v2.3.9 that patches the SSTI vulnerability, or implement proper input sanitization/sandboxing for FreeMarker templates before rendering.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60355 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-60355 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data