# CVE-2025-15141: Halo Configuration actuator information disclosure

> Remote attackers can exploit the Halo CMS configuration actuator to disclose sensitive information, requiring high complexity and permissions.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Dec 2025
- **Updated:** 24 Feb 2026
- **Also known as:** GHSA-9mf8-q5hw-h59m

## What is CVE-2025-15141?

CVE-2025-15141 is a low-severity vulnerability in Halo, published on 28 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was determined in Halo up to 2.21.10. This issue affects some unknown processing of the file /actuator of the component Configuration Handler. Executing a manipulation can lead to information disclosure. The attack may be performed from remote. This attack is characterized by high complexity. The exploitability is assessed as difficult. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-15141?

It affects 1 product.


Products: Halo Halo.

## How do I fix CVE-2025-15141?

No fix has been published for CVE-2025-15141 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-15141 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15141 exists.

## Other vulnerabilities in Halo

- [CVE-2022-32994](https://insights.sbomify.com/CVE-2022-32994/): File upload in n/a (critical 9.8)
- [CVE-2022-32995](https://insights.sbomify.com/CVE-2022-32995/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2020-18980](https://insights.sbomify.com/CVE-2020-18980/): Code injection in n/a (critical 9.8)
- [CVE-2020-21522](https://insights.sbomify.com/CVE-2020-21522/): Path traversal in n/a (critical 9.8)
- [CVE-2020-21523](https://insights.sbomify.com/CVE-2020-21523/): Code injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-15141 and fix it if it is affected.

What it is: CVE-2025-15141 is a low-severity vulnerability in Halo, published on 28 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15141 exists.

Affected product: Halo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-15141/ (Markdown: https://insights.sbomify.com/CVE-2025-15141/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-15141
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-15141
- OSV: https://osv.dev/vulnerability/CVE-2025-15141

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-15141/
Summaries are generated and may contain mistakes; the official description above is the record.
