# CVE-2026-6796: Sanluan PublicCMS Failed Login LoginAdminController.java log_login cleartext storage in file

> Remote attackers can access cleartext passwords stored in log files due to improper handling of failed login attempts in PublicCMS.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X`)
- **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:** 21 Apr 2026
- **Updated:** 21 Apr 2026
- **Also known as:** GHSA-crfw-8vvm-pm25

## What is CVE-2026-6796?

CVE-2026-6796 is a medium-severity vulnerability in Sanluan PublicCMS, published on 21 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was determined in Sanluan PublicCMS up to 6.202506.d. Affected is the function log_login of the file core/src/main/java/com/publiccms/controller/admin/LoginAdminController.java of the component Failed Login Handler. This manipulation of the argument errorPassword causes cleartext storage in a file or on disk. It is possible to initiate the attack remotely. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-313 (Cleartext Storage in a File or on Disk), CWE-312 (Cleartext Storage of Sensitive Information)

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


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

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

## Is CVE-2026-6796 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6796 is a medium-severity vulnerability in Sanluan PublicCMS, published on 21 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6796 in the wild and no public exploit code.

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

## Sources

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

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