CVE-2025-3594
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 · uneditedPath traversal vulnerability with the downloading and installation of Xuggler in Liferay Portal 7.0.0 through 7.4.3.4, and Liferay DXP 7.4 GA, 7.3 GA through update 34, and older unsupported versions allows remote attackers to (1) add files to arbitrary locations on the server and (2) download and execute arbitrary files from the download server via the `_com_liferay_server_admin_web_portlet_ServerAdminPortlet_jarName` parameter.
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 · high confidenceA path traversal vulnerability in Liferay Portal and DXP's ServerAdminPortlet allows remote attackers to manipulate the jarName parameter to write files to arbitrary locations on the server and download/execute malicious files from remote servers during Xuggler installation, enabling full remote code execution.
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>= 7.0, <= 7.2= 7.3= 7.4>= 7.0.0, <= 7.4.3.4= 6.2CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 your Lifer Portal or DXP versionAccess the Lifer Control Panel or check the portal-ext.properties file for the version number. In the Control Panel, go to Configuration > Server Administration > General (or check the welcome page for version info).Affected if The installed version falls within 7.0 to 7.4 (inclusive), or is exactly 7.3 or 7.4, or is 6.2. Versions 7.4.3.5 and later are NOT affected.
-
Verify if ServerAdminPortlet is accessibleCheck if the Server Admin portlet endpoint is available. Typical paths include /server_admin or /c/server_admin. Attempt to access this endpoint with administrative credentials.Affected if The ServerAdminPortlet is exposed and accessible to the attacker (authenticated admin or compromised admin session).
-
Determine if Xuggler installation functionality existsLook for Xuggler-related configuration or installation modules in the Lifer deployment. Check for any Xuggler JAR files in the liferay-home directory or under the osgi/modules folder.Affected if Xuggler installation functionality is present or was previously installed on the system.
-
Inspect for suspicious files in unexpected locationsSearch the filesystem for newly created JAR files in directories outside the expected Lifer deployment structure (for example, in webroot, temp, or system directories). Use file system integrity tools or compare against known-good baselines.Affected if Unexpected JAR files exist in arbitrary locations outside the standard Lifer deployment directories.
-
Review server access logs for ServerAdminPortlet activityExamine web server and Lifer logs for requests to the Server Admin portlet, particularly those containing unusual jarName parameter values or Xuggler-related operations.Affected if Logs show requests to ServerAdminPortlet with abnormal jarName parameter values or Xuggler installation attempts.
You are affected if you run Lifer Portal 7.0.0-7.4.3.4, Lifer DXP 7.0-7.4, or Lifer Portal 6.2, and the ServerAdminPortlet with Xuggler installation functionality is accessible to potentially malicious users.
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.
From vendor dataUpgrade LiferPortal to 7.4.3.5 or later and LiferDXP to the latest available patch/fix pack that addresses this vulnerability. If immediate patching is not possible, restrict access to the Server Admin portlet or disable Xuggler installation functionality.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3594 — 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-3594 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