# CVE-2025-3027: Open Redirect vulnerability in EJBCA

> Attackers can redirect users to malicious external sites via URL manipulation, facilitating phishing attacks against EJBCA users.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 31 Mar 2025
- **Updated:** 31 Mar 2025
- **Also known as:** BIT-ejbca-2025-3027, GHSA-m97g-5q6h-6fcq

## What is CVE-2025-3027?

CVE-2025-3027 is a medium-severity vulnerability in PrimeKey Solutions AB EJBCA, published on 31 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The vulnerability exists in the EJBCA service, version 8.0 Enterprise. By making a small change to the PATH of the URL associated with the service, the server fails to find the requested file and redirects to an external page. This vulnerability could allow users to be redirected to potentially malicious external sites, which can be exploited for phishing or other social engineering attacks.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

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

1 open source package ship an affected version, including ejbca. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ejbca` | Bitnami | From 8.0.0 | 9.1.0 |

Products: Primekey Ejbca.

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

Upgrade ejbca to 9.1.0 or later.

## Is CVE-2025-3027 being exploited?

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

## Other vulnerabilities in PrimeKey Solutions AB EJBCA

- [CVE-2022-34831](https://insights.sbomify.com/CVE-2022-34831/): Business logic in n/a (critical 9.8)
- [CVE-2020-11630](https://insights.sbomify.com/CVE-2020-11630/): Deserialization in n/a (critical 9.8)
- [CVE-2020-11627](https://insights.sbomify.com/CVE-2020-11627/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2020-25276](https://insights.sbomify.com/CVE-2020-25276/): Security feature bypass in n/a (high 7.3)
- [CVE-2020-11629](https://insights.sbomify.com/CVE-2020-11629/): File upload in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3027 is a medium-severity vulnerability in PrimeKey Solutions AB EJBCA, published on 31 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-3027 in the wild and no public exploit code.

Affected packages and fixed versions:
- ejbca (Bitnami): affected from 8.0.0; fixed in 9.1.0

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-3027/ (Markdown: https://insights.sbomify.com/CVE-2025-3027/index.md)
```

## Sources

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

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