# CVE-2026-15933: Cleartext Storage of Sensitive Credentials in OptimiDoc Server (On-Premise)

> An authenticated administrator can view cleartext credentials for external services like SMTP and Active Directory in the web administration panel source code.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Sep 2026
- **Updated:** 3 Sep 2026
- **Also known as:** GHSA-932v-hwxh-w7jw

## What is CVE-2026-15933?

CVE-2026-15933 is a medium-severity vulnerability in OptimiDoc Server, published on 3 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

OptimiDoc Server (On-Premise) stores credentials for external services in cleartext. An authenticated administrator can view previously configured service passwords, including SMTP, FTP (for scan delivery), Active Directory (for user list import), and SharePoint credentials, in cleartext via the web administration panel page source, allowing exposure of sensitive third-party authentication data.

This issue was fixed in version 26.08

Weakness: CWE-256 (Plaintext Storage of a Password)

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


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

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

## Is CVE-2026-15933 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15933 is a medium-severity vulnerability in OptimiDoc Server, published on 3 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-15933 in the wild and no public exploit code.

Affected product: OptimiDoc Server. 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-15933/ (Markdown: https://insights.sbomify.com/CVE-2026-15933/index.md)
```

## Sources

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

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