dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-62276

MEDIUM · 5.5 CVSS v3.1 Published 2025-11-01
Fix available
A fix is available. Upgrade to 7.4.3.112 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
The Document Library and the Adaptive Media modules in Liferay Portal 7.4.0 through 7.4.3.111, and older unsupported versions, and Liferay DXP 2023.Q4.0 through 2023.Q4.10, 2023.Q3.1 through 2023.Q3.10, 7.4 GA through update 92, and older unsupported versions uses an incorrect cache-control header, which allows local users to obtain access to downloaded files via the browser's cache.

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 confidence

The Document Library and Adaptive Media modules in Liferium Portal and DXP set incorrect cache-control headers on downloaded files, causing browsers to cache sensitive documents locally. This allows local users on shared computers to access previously downloaded files through the browser cache.

MitigationConfigure proper cache-control headers (no-store, no-cache, must-revalidate, private) for file downloads in the Document Library and Adaptive Media modules to prevent browser caching of sensitive documents.

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
Digital Experience PlatformApplication
Affected:= 7.4= 2023.q3.1= 2023.q3.2= 2023.q3.3= 2023.q3.4= 2023.q3.5= 2023.q3.6= 2023.q3.7= 2023.q3.8= 2023.q3.9= 2023.q3.10= 2023.q4.0
Liferay PortalApplication
Affected:>= 7.4.0, < 7.4.3.112

CVSS 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Lifteral DXP/Portal version
    Access the Liferay Control Panel (Control Panel > Configuration > System Information) or check the portal-ext.properties file for the version property, or query the OSGi console with 'lb | grep liferay-portal'
    Affected if The version matches 7.4, any 2023.q3.x (q3.1 through q3.10), 2023.q4.0, or is >= 7.4.0 but < 7.4.3.112
  2. Verify Document Library module is active
    In the OSGi Felix console (http://server:port/o/felix-console), search for 'com-liferay-document-library' or check the Document Library portlet is deployed in the Control Panel under Content > Document Library
    Affected if Document Library is present and functional on the portal
  3. Verify Adaptive Media module is active
    In the OSGi Felix console, search for 'com-ladaptive-media' or check if Adaptive Media is enabled under Control Panel > Configuration > Adaptive Media
    Affected if Adaptive Media is enabled and processing images or documents
  4. Inspect cache-control headers for Document Library downloads
    Download a test file from the Document Library (navigate to a document, use browser DevTools Network tab or run curl -I on the download URL), then examine the HTTP response headers for the 'Cache-Control' header
    Affected if Cache-Control header is missing, or set to 'public', 'max-age', or any value other than 'no-store, no-cache, must-revalidate, private' (or similar restrictive directive)
  5. Inspect cache-control headers for Adaptive Media downloads
    Request a media file processed by Adaptive Media (image or document thumbnail), examine the HTTP response headers for the 'Cache-Control' header using curl -I or browser DevTools
    Affected if Cache-Control header is missing, or set to 'public', 'max-age', or any value that permits browser caching

A user is affected if running a Liferay DXP or Portal version listed in the affected range AND uses Document Library or Adaptive Media modules AND the Cache-Control headers on downloaded files do not contain restrictive directives (no-store, no-cache, must-revalidate, or private).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.4.3.112 or later
Fixed in 7.4.3.112
Interim mitigation

Configure proper cache-control headers (no-store, no-cache, must-revalidate, private) for file downloads in the Document Library and Adaptive Media modules to prevent browser caching of sensitive documents.

Recommended fix High confidence

Liferay Portal 7.4.3.112+ or Lifera DXP 2023.Q4.11+/2023.Q3.11+/7.4 GA update 93+

  1. 1. Backup your current Liferay instance and database before proceeding with any upgrade.
  2. 2. For Liferay Portal 7.4.x users: Upgrade to version 7.4.3.112 or later.
  3. 3. For Liferay DXP users: Upgrade to one of the following fixed releases: 2023.Q4.11, 2023.Q3.11, or 7.4 GA update 93 or later.
  4. 4. After upgrading, verify that the Document Library and Adaptive Media modules are functioning correctly.
  5. 5. Clear browser caches and test that proper cache-control headers are being sent for downloaded files.
  6. 6. If running in a clustered environment, ensure all nodes are upgraded to the same fixed version.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-62276 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-62276 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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