# CVE-2026-78971: Halo CMS plugin management arbitrary code execution

Source: https://junglewise.ai/threats/cve-2026-78971-halo-cms-plugin-management-arbitrary-code-execution  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-08. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-78971 · Severity: medium · CVSS 4.6 · Published 2026-09-08

Halo is an open-source website building platform used for blogs, knowledge bases, and e-commerce sites. Versions 2.25.4 and earlier contain a vulnerability in the plugin management system that allows attackers to install or update malicious plugins, leading to arbitrary command execution with the privileges of the Halo process. This could enable attackers to compromise the web server, steal data, or deploy further attacks.

Technologies: [Halo](https://junglewise.ai/threats/technologies/halo). Vendors: [Halo](https://junglewise.ai/threats/vendors/halo).

## Quick answers

**Is CVE-2026-78971 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-78971 being exploited in the wild.

**How severe is CVE-2026-78971?** Medium severity, with a CVSS score of 4.6, published 8 September 2026.

**Which products and versions are affected?** Halo ≤ 2.25.4.

**Is there a fix for CVE-2026-78971?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-78971 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-78971?** Check whether you run Halo at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability exists in Halo's plugin management feature (versions ≤ 2.25.4), which fails to properly validate or sanitize plugins during installation/update operations. The insufficient input validation allows attackers to upload malicious plugins that execute arbitrary commands with the permissions of the Halo process. The attack requires authenticated access to the plugin management interface, but once exploited, an attacker gains remote code execution (RCE) on the server. No patch information was provided in the advisory, but the issue is tracked as CVE-2026-78971.

## Affected products

- Halo Halo ≤ 2.25.4

## Timeline

- 2026-09-08: disclosed

## References

- [https://github.com/LING12138-sg/MyCVE-Report/issues/1](https://github.com/LING12138-sg/MyCVE-Report/issues/1)
- [https://github.com/halo-dev/halo](https://github.com/halo-dev/halo)

## Related threats

- [Halo open redirect vulnerability in thumbnail endpoint](https://junglewise.ai/threats/cve-2026-91772-halo-open-redirect-vulnerability-in-thumbnail-endpoint)
- [halo-dev Halo path traversal in Files Backup Endpoint](https://junglewise.ai/threats/cve-2026-16088-halo-dev-halo-path-traversal-in-files-backup-endpoint)
- [halo-dev Halo path traversal in Theme Installation](https://junglewise.ai/threats/cve-2026-15326-halo-dev-halo-path-traversal-in-theme-installation)
- [Halo path traversal in backup download endpoint](https://junglewise.ai/threats/cve-2026-55439-halo-path-traversal-in-backup-download-endpoint)
- [A vulnerability was determined in Halo up to 2.21.10. This issue affects some unknown processing of the file /actuator…](https://junglewise.ai/threats/cve-2025-15141-a-vulnerability-was-determined-in-halo-up-to-2-21-10-this-issue)