Halo
Monthly
Let me produce the JSON. Product: Halo (halo-dev) — a Java CMS/blog platform. Product name: "Halo". Summary: Open redirect in anonymous thumbnail endpoint, uri param unvalidated. Halo through 2.26.1. CVSS 4.0: AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N — base likely 5.3. Note: no patch info explicitly. References include issue #10247 — likely the fix issue. No exact fix version. So "Upstream fix available (PR/commit); released patched version not independently confirmed"? Hmm — the issue link is an untagged cveorg reference. I'd say "No vendor-released patch identified at time of analysis" — but there's an issue link. Let me phrase carefully: no patch version confirmed in the provided data; the issue reference may track remediation. Prevalence: Halo is a Chinese open-source blogging/CMS platform — medium? It's a popular Java-based CMS/blog framework in China with GitHub ~36k stars. Deployment footprint: medium seems fair. Actually blogging platforms — I'd say medium. Assessed CVSS 3.1: AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N → 6.1? Wait, CVSS 4.0 gave 5.3 with UI:P (passive). In 3.1, UI:R. Scope: open redirect — does it cross trust boundary? Typically scope unchanged. C:L/I:L? The 4.0 vector has SC:L/SI:L which implies the subsequent system (the redirect target) has low confidentiality/integrity impact. In 3.1 that would suggest S:C. So AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N → 6.1. Hmm. Alternatively S:U → 4.3? Let's compute: AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N = 5.4? Let's check: base with C:L/I:L — impact sub score = 1 - (1-0.22)(1-0.22)(1-0) = 1-0.6084 = 0.3916. ISS = 6.42*0.3916 = 2.514. Exploitability = 8.22*1*1*1*0.62 = 5.096. Base = roundup(min(2.514+5.096, 10)) = roundup(7.61) = 7.6? Hmm, that seems too high. Wait: with S:U, Impact = 6.42*ISS = 6.42*0.3916=2.514. Base score = roundup(min(Impact+Exploitability,10)) = roundup(7.61)=7.6. Hmm, that's for C:L/I:L. Hmm but that requires multiplying 1.08? No, only for S:C: Impact = 7.52*(ISS-0.029) - 3.2
Path traversal in halo-dev/halo through version 2.24.2 allows authenticated administrators to write files outside the intended theme directory by supplying a crafted `metadata.name` value during theme installation. The flaw resides in the `ThemeUtils.unzipThemeTo()` function in `ThemeUtils.java`, which fails to sanitize the metadata name before constructing extraction paths. A public proof-of-concept exploit exists, but real-world impact is substantially constrained by the PR:H prerequisite - the attacker must already hold admin-level credentials - yielding a CVSS 4.0 score of only 2.0 and no CISA KEV listing.
Path traversal in Halo's backup download endpoint allows authenticated administrators to read arbitrary files from the server filesystem, bypassing directory boundaries. Affected are all Halo deployments prior to version 2.24.3, where the MigrationServiceImpl.download() method invokes Path.resolve() on attacker-supplied filenames without enforcing containment within the designated backups directory. A compounding issue exists in the backup creation endpoint, which fails to sanitize status fields. No public exploit code or CISA KEV listing has been identified at time of analysis, and the PR:H requirement meaningfully constrains the attack surface.
An issue in halo v.2.22.4 and before allows a remote attacker to cause a denial of service via a crafted payload to the public comment submission endpoint [CVSS 7.5 HIGH]
Information disclosure in Halo up to 2.21.10 can be triggered by a remote attacker with low privileges via high-complexity manipulation of the /actuator configuration handler, potentially leaking limited configuration data. Public exploit code exists, but active exploitation has not been confirmed and EPSS indicates a negligible exploitation probability (0.03%). The low CVSS 4.0 score and high attack complexity further reduce the real-world
Cross-site request forgery in fit2cloud Halo 2.21.10 allows remote attackers to perform unauthorized actions on behalf of authenticated users. A publicly available proof-of-concept exploit exists, though no active exploitation has been confirmed. The vendor was contacted but did not respond, leaving the vulnerability unpatched.
Halo v2.20.17 and before is vulnerable to Cross Site Scripting (XSS) in /halo_host/archives/{name}. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
Halo prior to 2.20.13 allows bypassing file type detection and uploading malicious files such as .exe and .html files. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
halo v2.20.17 and before is vulnerable to server-side request forgery (SSRF) in /apis/uc.api.storage.halo.run/v1alpha1/attachments/-/upload-from-url. Rated critical severity (CVSS 9.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
Halo is an open source website building tool. Rated medium severity (CVSS 5.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
Halo is an open source website building tool. Rated medium severity (CVSS 6.4), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
Halo is an open source website building tool. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
An arbitrary file upload vulnerability in Halo up to v1.6.1 allows attackers to execute arbitrary code via a crafted .md file. Rated medium severity (CVSS 4.8), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
Halo CMS v1.5.3 was discovered to contain a Server-Side Request Forgery (SSRF) via the template remote download function. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
Halo CMS v1.5.3 was discovered to contain an arbitrary file upload vulnerability via the component /api/admin/attachments/upload. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
Halo-1.5.0 was discovered to contain a stored cross-site scripting (XSS) vulnerability via \admin\index.html#/system/tools. Rated medium severity (CVSS 4.8), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
Halo Blog CMS v1.4.17 was discovered to allow attackers to upload arbitrary files via the Attachment Upload function. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
There is an Arbitrary file deletion vulnerability in halo v1.1.3. Rated high severity (CVSS 7.7), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
An Arbitrary file writing vulnerability in halo v1.1.3. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
Halo V1.1.3 is affected by: Arbitrary File reading. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
There is a XML external entity (XXE) vulnerability in halo v1.1.3, The function of importing other blogs in the background(/api/admin/migrations/wordpress) needs to parse the xml file, but it is not. Rated critical severity (CVSS 9.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
A Server-Side Freemarker template injection vulnerability in halo CMS v1.1.3 In the Edit Theme File function. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
An issue was discovered in halo V1.1.3. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
Halo blog 1.2.0 allows users to submit comments on blog posts via /api/content/posts/comments. Rated medium severity (CVSS 5.4), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
Halo before 1.2.0-beta.1 allows Server Side Template Injection (SSTI) because TemplateClassResolver.SAFER_RESOLVER is not used in the FreeMarker configuration. Rated high severity (CVSS 7.2), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available.
Halo 1.1.0 has XSS via a crafted authorUrl in JSON data to api/content/posts/comments. Rated medium severity (CVSS 5.4), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
ruibaby Halo 0.0.2 has stored XSS via the loginName and loginPwd parameters in a failed login attempt to AdminController.java. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
ruibaby Halo 0.0.2 has stored XSS via the commentAuthor field to FrontCommentController.java. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
Let me produce the JSON. Product: Halo (halo-dev) — a Java CMS/blog platform. Product name: "Halo". Summary: Open redirect in anonymous thumbnail endpoint, uri param unvalidated. Halo through 2.26.1. CVSS 4.0: AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N — base likely 5.3. Note: no patch info explicitly. References include issue #10247 — likely the fix issue. No exact fix version. So "Upstream fix available (PR/commit); released patched version not independently confirmed"? Hmm — the issue link is an untagged cveorg reference. I'd say "No vendor-released patch identified at time of analysis" — but there's an issue link. Let me phrase carefully: no patch version confirmed in the provided data; the issue reference may track remediation. Prevalence: Halo is a Chinese open-source blogging/CMS platform — medium? It's a popular Java-based CMS/blog framework in China with GitHub ~36k stars. Deployment footprint: medium seems fair. Actually blogging platforms — I'd say medium. Assessed CVSS 3.1: AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N → 6.1? Wait, CVSS 4.0 gave 5.3 with UI:P (passive). In 3.1, UI:R. Scope: open redirect — does it cross trust boundary? Typically scope unchanged. C:L/I:L? The 4.0 vector has SC:L/SI:L which implies the subsequent system (the redirect target) has low confidentiality/integrity impact. In 3.1 that would suggest S:C. So AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N → 6.1. Hmm. Alternatively S:U → 4.3? Let's compute: AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N = 5.4? Let's check: base with C:L/I:L — impact sub score = 1 - (1-0.22)(1-0.22)(1-0) = 1-0.6084 = 0.3916. ISS = 6.42*0.3916 = 2.514. Exploitability = 8.22*1*1*1*0.62 = 5.096. Base = roundup(min(2.514+5.096, 10)) = roundup(7.61) = 7.6? Hmm, that seems too high. Wait: with S:U, Impact = 6.42*ISS = 6.42*0.3916=2.514. Base score = roundup(min(Impact+Exploitability,10)) = roundup(7.61)=7.6. Hmm, that's for C:L/I:L. Hmm but that requires multiplying 1.08? No, only for S:C: Impact = 7.52*(ISS-0.029) - 3.2
Path traversal in halo-dev/halo through version 2.24.2 allows authenticated administrators to write files outside the intended theme directory by supplying a crafted `metadata.name` value during theme installation. The flaw resides in the `ThemeUtils.unzipThemeTo()` function in `ThemeUtils.java`, which fails to sanitize the metadata name before constructing extraction paths. A public proof-of-concept exploit exists, but real-world impact is substantially constrained by the PR:H prerequisite - the attacker must already hold admin-level credentials - yielding a CVSS 4.0 score of only 2.0 and no CISA KEV listing.
Path traversal in Halo's backup download endpoint allows authenticated administrators to read arbitrary files from the server filesystem, bypassing directory boundaries. Affected are all Halo deployments prior to version 2.24.3, where the MigrationServiceImpl.download() method invokes Path.resolve() on attacker-supplied filenames without enforcing containment within the designated backups directory. A compounding issue exists in the backup creation endpoint, which fails to sanitize status fields. No public exploit code or CISA KEV listing has been identified at time of analysis, and the PR:H requirement meaningfully constrains the attack surface.
An issue in halo v.2.22.4 and before allows a remote attacker to cause a denial of service via a crafted payload to the public comment submission endpoint [CVSS 7.5 HIGH]
Information disclosure in Halo up to 2.21.10 can be triggered by a remote attacker with low privileges via high-complexity manipulation of the /actuator configuration handler, potentially leaking limited configuration data. Public exploit code exists, but active exploitation has not been confirmed and EPSS indicates a negligible exploitation probability (0.03%). The low CVSS 4.0 score and high attack complexity further reduce the real-world
Cross-site request forgery in fit2cloud Halo 2.21.10 allows remote attackers to perform unauthorized actions on behalf of authenticated users. A publicly available proof-of-concept exploit exists, though no active exploitation has been confirmed. The vendor was contacted but did not respond, leaving the vulnerability unpatched.
Halo v2.20.17 and before is vulnerable to Cross Site Scripting (XSS) in /halo_host/archives/{name}. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
Halo prior to 2.20.13 allows bypassing file type detection and uploading malicious files such as .exe and .html files. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
halo v2.20.17 and before is vulnerable to server-side request forgery (SSRF) in /apis/uc.api.storage.halo.run/v1alpha1/attachments/-/upload-from-url. Rated critical severity (CVSS 9.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
Halo is an open source website building tool. Rated medium severity (CVSS 5.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
Halo is an open source website building tool. Rated medium severity (CVSS 6.4), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
Halo is an open source website building tool. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
An arbitrary file upload vulnerability in Halo up to v1.6.1 allows attackers to execute arbitrary code via a crafted .md file. Rated medium severity (CVSS 4.8), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
Halo CMS v1.5.3 was discovered to contain a Server-Side Request Forgery (SSRF) via the template remote download function. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
Halo CMS v1.5.3 was discovered to contain an arbitrary file upload vulnerability via the component /api/admin/attachments/upload. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
Halo-1.5.0 was discovered to contain a stored cross-site scripting (XSS) vulnerability via \admin\index.html#/system/tools. Rated medium severity (CVSS 4.8), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
Halo Blog CMS v1.4.17 was discovered to allow attackers to upload arbitrary files via the Attachment Upload function. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
There is an Arbitrary file deletion vulnerability in halo v1.1.3. Rated high severity (CVSS 7.7), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
An Arbitrary file writing vulnerability in halo v1.1.3. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
Halo V1.1.3 is affected by: Arbitrary File reading. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
There is a XML external entity (XXE) vulnerability in halo v1.1.3, The function of importing other blogs in the background(/api/admin/migrations/wordpress) needs to parse the xml file, but it is not. Rated critical severity (CVSS 9.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
A Server-Side Freemarker template injection vulnerability in halo CMS v1.1.3 In the Edit Theme File function. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
An issue was discovered in halo V1.1.3. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
Halo blog 1.2.0 allows users to submit comments on blog posts via /api/content/posts/comments. Rated medium severity (CVSS 5.4), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
Halo before 1.2.0-beta.1 allows Server Side Template Injection (SSTI) because TemplateClassResolver.SAFER_RESOLVER is not used in the FreeMarker configuration. Rated high severity (CVSS 7.2), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available.
Halo 1.1.0 has XSS via a crafted authorUrl in JSON data to api/content/posts/comments. Rated medium severity (CVSS 5.4), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
ruibaby Halo 0.0.2 has stored XSS via the loginName and loginPwd parameters in a failed login attempt to AdminController.java. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
ruibaby Halo 0.0.2 has stored XSS via the commentAuthor field to FrontCommentController.java. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.