CVE-2025-3027
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is an open redirect vulnerability in EJBCA Enterprise version 8.0. By manipulating the PATH component of the service URL (changing it slightly), the server fails to locate the requested resource and instead redirects the user to an external URL. Attackers can exploit this to craft malicious links that appear to point to the legitimate EJBCA service but actually redirect users to attacker-controlled sites for phishing or credential theft.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 8.0, < 9.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify EJBCA installation and versionLocate the EJBCA installation directory and check for version files such as VERSION.txt, build.properties, or the war/ear file name. Common paths include /opt/ejbca, /usr/share/ejbca, or the application server's deploy directory. Run: find / -name 'ejbca*' -type f 2>/dev/null | head -20 to locate installation files.Affected if The installed version is EJBCA Enterprise 8.0.x (any minor version) or if the version cannot be determined but the software is identified as EJBCA from the Primekey vendor.
-
Check application server logs for redirect patternsReview HTTP access logs from the underlying application server (typically WildFly, JBoss, or Tomcat) for patterns where the PATH results in a 302/303 redirect to an external domain. Look for log entries showing redirects to non-localhost/non-internal domains after a request to the EJBCA context path.Affected if Logs show 3xx redirects to external URLs (domains not matching the server's hostname or internal IP ranges) when accessing EJBCA endpoints.
-
Inspect web server or proxy configurationExamine the configuration of any reverse proxy (Apache, Nginx, HAProxy) or load balancer in front of EJBCA. Check for rewrite rules or proxy configurations that may not be filtering external redirect targets. Review proxy.conf, nginx.conf, or httpd.conf files.Affected if The proxy configuration lacks validation rules to block or rewrite external redirect Location headers originating from the EJBCA application.
-
Verify EJBCA is exposed on networkConfirm EJBCA web interface is accessible externally or via untrusted networks. Check firewall rules, security groups, or network ACLs: iptables -L -n or cloud security group inbound rules. Identify if port 8080, 8443, or the configured HTTP/HTTPS port is open to non-trusted sources.Affected if The EJBCA web interface is accessible from networks where potential phishing victims could be directed to the malicious redirect link.
You are affected if EJBCA Enterprise version 8.0.x is installed and accessible over the network, as the open redirect vulnerability exists in all versions from 8.0 up to (but not including) 9.1.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped9.1
Upgrade to a patched version of EJBCA if available; otherwise, implement URL validation or proxy rules to block external redirects and ensure the application only redirects to internal, validated paths.
EJBCA 9.1
- 1. Review the EJBCA upgrade documentation for version 9.1
- 2. Create a full backup of the current EJBCA installation including database and configuration
- 3. Test the upgrade in a non-production environment first
- 4. Schedule a maintenance window for the production upgrade
- 5. Stop the EJBCA service
- 6. Run the upgrade procedure to version 9.1 following official upgrade guides
- 7. Verify the installation and ensure all services start correctly
- 8. Test that the open redirect vulnerability is no longer present by attempting URL manipulation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3027 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-3027 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data