# CVE-2023-25263: Weak cryptography in n/a

> Attackers can decrypt connection strings in .mrt files using a static secret, exposing sensitive database credentials.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Mar 2023
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-v4pr-w7x8-m4mg

## What is CVE-2023-25263?

CVE-2023-25263 is a medium-severity vulnerability in n/a, published on 27 Mar 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Stimulsoft Designer (Desktop) 2023.1.5, and 2023.1.4, once an attacker decompiles the Stimulsoft.report.dll the attacker is able to decrypt any connectionstring stored in .mrt files since a static secret is used. The secret does not differ between the tested versions and different operating systems.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2023-25263?

It affects 1 product.


Products: Stimulsoft Designer.

## How do I fix CVE-2023-25263?

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

## Is CVE-2023-25263 being exploited?

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

Public exploit code:

- https://github.com/trustcves/CVE-2023-25263 (github_poc): https://github.com/trustcves/CVE-2023-25263

## Other vulnerabilities in n/a

- [CVE-2023-25261](https://insights.sbomify.com/CVE-2023-25261/): Code injection in n/a (critical 9.8)
- [CVE-2023-25260](https://insights.sbomify.com/CVE-2023-25260/): Path traversal in n/a (high 7.5)
- [CVE-2023-25262](https://insights.sbomify.com/CVE-2023-25262/): Server-side request forgery in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-25263 and fix it if it is affected.

What it is: CVE-2023-25263 is a medium-severity vulnerability in n/a, published on 27 Mar 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-25263 exists.

Affected product: n/a. 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-2023-25263/ (Markdown: https://insights.sbomify.com/CVE-2023-25263/index.md)
```

## Sources

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

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