# CVE-2025-27223: Hardcoded credentials in n/a

> Attackers can forge authentication cookies using a static key to bypass authentication and access sensitive internal information in TRUfusion Enterprise.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 27 Oct 2025
- **Updated:** 28 Oct 2025
- **Also known as:** GHSA-x7xc-36fh-7mvr

## What is CVE-2025-27223?

CVE-2025-27223 is a high-severity vulnerability in n/a, published on 27 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TRUfusion Enterprise through 7.10.4.0 exposes the encrypted COOKIEID as an authentication mechanism for some endpoints such as /trufusionPortal/getProjectList. However, the application uses a static key to create the encrypted cookie, ultimately allowing anyone to forge cookies and gain access to sensitive internal information.

Weakness: CWE-1004 (Sensitive Cookie Without 'HttpOnly' Flag)

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

It affects 1 product.


Products: Rocketsoftware Trufusion Enterprise.

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

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

## Is CVE-2025-27223 being exploited?

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

Public exploit code:

- TRUfusion Enterprise <= 7.10.4.0 - Authentication Bypass (nuclei): http/cves/2025/CVE-2025-27223.yaml

## Other vulnerabilities in n/a

- [CVE-2025-27224](https://insights.sbomify.com/CVE-2025-27224/): Path traversal in n/a (critical 9.8)
- [CVE-2025-59793](https://insights.sbomify.com/CVE-2025-59793/): Path traversal in n/a (critical 9.4)
- [CVE-2025-27222](https://insights.sbomify.com/CVE-2025-27222/): Path traversal in n/a (high 8.6)
- [CVE-2025-32355](https://insights.sbomify.com/CVE-2025-32355/): Server-side request forgery in n/a (high 7.9)
- [CVE-2025-27225](https://insights.sbomify.com/CVE-2025-27225/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-27223 is a high-severity vulnerability in n/a, published on 27 Oct 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-27223 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-2025-27223/ (Markdown: https://insights.sbomify.com/CVE-2025-27223/index.md)
```

## Sources

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

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