# CVE-2025-15151: TaleLin Lin-CMS Tests Folder config.py password in configuration file

> Hardcoded credentials in the Lin-CMS test configuration file allow remote attackers to potentially access sensitive data or take over accounts.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Dec 2025
- **Updated:** 29 Dec 2025
- **Also known as:** GHSA-xc62-88x4-447w

## What is CVE-2025-15151?

CVE-2025-15151 is a medium-severity vulnerability in TaleLin Lin-CMS, published on 28 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was determined in TaleLin Lin-CMS up to 0.6.0. This affects an unknown part of the file /tests/config.py of the component Tests Folder. This manipulation of the argument username/password causes password in configuration file. The attack is possible to be carried out remotely. The complexity of an attack is rather high. It is indicated that the exploitability is difficult. The exploit has been publicly disclosed and may be utilized.

Weakness: CWE-260 (Password in Configuration File), CWE-255

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


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

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

## Is CVE-2025-15151 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15151 is a medium-severity vulnerability in TaleLin Lin-CMS, published on 28 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15151 exists.

Affected product: TaleLin Lin-CMS. 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-15151/ (Markdown: https://insights.sbomify.com/CVE-2025-15151/index.md)
```

## Sources

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

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