# CVE-2025-47730: Hardcoded credentials in archiving backend

> Hardcoded credentials in the TeleMessage archiving backend allow attackers to obtain authentication tokens and access user data.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/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:** 8 May 2025
- **Updated:** 8 May 2025
- **Also known as:** GHSA-9qc4-m2hc-5vc5

## What is CVE-2025-47730?

CVE-2025-47730 is a medium-severity vulnerability in TeleMessage archiving backend, published on 8 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The TeleMessage archiving backend through 2025-05-05 accepts API calls (to request an authentication token) from the TM SGNL (aka Archive Signal) app with the credentials of logfile for the user and enRR8UVVywXYbFkqU#QDPRkO for the password.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Smarsh Telemessage.

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

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

## Is CVE-2025-47730 being exploited?

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

## Other vulnerabilities in TeleMessage archiving backend

- [CVE-2025-48927](https://insights.sbomify.com/CVE-2025-48927/): TeleMessage TM SGNL Initialization of a Resource with an Insecure Default (medium 5.3, exploited in the wild)
- [CVE-2025-48928](https://insights.sbomify.com/CVE-2025-48928/): TeleMessage TM SGNL Exposure of Core Dump File to an Unauthorized Control Sphere (medium 4.0, exploited in the wild)
- [CVE-2025-48925](https://insights.sbomify.com/CVE-2025-48925/): Weak cryptography in service (medium 4.3)
- [CVE-2025-48926](https://insights.sbomify.com/CVE-2025-48926/): Information disclosure in service (medium 4.3)
- [CVE-2025-48929](https://insights.sbomify.com/CVE-2025-48929/): Auth bypass in service (medium 4.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-47730 is a medium-severity vulnerability in TeleMessage archiving backend, published on 8 May 2025. 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-2025-47730 in the wild and no public exploit code.

Affected product: TeleMessage archiving backend. 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-47730/ (Markdown: https://insights.sbomify.com/CVE-2025-47730/index.md)
```

## Sources

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

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