Skip to main content
CVE-2025-60355VulnerabilityPublished Updated

CVE-2025-60355: OneBlog · n/a

Affects OneBlogSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
GitHubline2222/OneBlogpkg:github/line2222/OneBlogOther threatsAffected
  • <=2.3.9
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately restrict or disable the use of FreeMarker templates that process user input until a patch is available. 2. Implement strict input validation and sanitization to ensure that user-supplied data cannot be interpreted as template directives. 3. Employ a Web Application Firewall (WAF) with custom rules to detect and block suspicious template injection patterns targeting FreeMarker. 4. Monitor application logs for unusual template processing activities or error messages indicative of injection attempts. 5. Isolate OneBlog instances in segmented network zones to limit potential lateral movement if compromised. 6. Regularly back up critical data and configurations to enable recovery in case of an attack. 7. Stay alert for official patches or updates from the OneBlog maintainers and apply them promptly once released. 8. Consider migrating to alternative blogging platforms with more secure template handling if immediate patching is not feasible.

Description

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

References

Community reviews

Loading reviews…