# CVE-2026-15575: Sensitive Information Disclosure Due to Enabled Debug Mode in Production in SFM Software's Costifier

> Attackers can access sensitive information and non-production interfaces due to debug mode being enabled in the Costifier application.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-mv4w-jq9r-p823

## What is CVE-2026-15575?

CVE-2026-15575 is a medium-severity vulnerability in SFM Software Technologies Inc. Costifier, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Active debug code vulnerability in SFM Software Technologies Inc. Costifier allows Exploit Non-Production Interfaces.

This issue affects Costifier: through 2026-10-16. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-489 (Active Debug Code)

## Which versions are affected by CVE-2026-15575?


## How do I fix CVE-2026-15575?

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

## Is CVE-2026-15575 being exploited?

There is no known exploitation of CVE-2026-15575 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-15575 and fix it if it is affected.

What it is: CVE-2026-15575 is a medium-severity vulnerability in SFM Software Technologies Inc. Costifier, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-15575 in the wild and no public exploit code.

Affected product: SFM Software Technologies Inc. Costifier. 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-2026-15575/ (Markdown: https://insights.sbomify.com/CVE-2026-15575/index.md)
```

## Sources

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

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