dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-62256

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-23
Fix available
A fix is available. Upgrade to 7.4.3.110 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Liferay Portal 7.4.0 through 7.4.3.109, and Liferay DXP 2023.Q4.0 through 2023.Q4.5, 2023.Q3.1 through 2023.Q3.7, 7.4 GA through update 92, 7.3 GA through update 35, and older unsupported versions does not properly restrict access to OpenAPI in certain circumstances, which allows remote attackers to access the OpenAPI YAML file via a crafted URL.

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

Lifter Portal and DXP versions fail to enforce proper access controls on OpenAPI endpoints, allowing unauthenticated remote attackers to retrieve the OpenAPI YAML file via specially crafted URLs. This exposes API documentation containing endpoint structures, parameter definitions, and potentially sensitive operational details.

MitigationConfigure web server or application-level access controls to restrict unauthorized access to OpenAPI endpoints and YAML files, limiting exposure to authenticated users only.

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.3= 7.4= 2023.q3.1= 2023.q3.2= 2023.q3.3= 2023.q3.4= 2023.q3.5= 2023.q3.6= 2023.q3.7= 2023.q4.0= 2023.q4.1= 2023.q4.2
Liferay PortalApplication
Affected:>= 7.4.0, < 7.4.3.110

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 installed Lifer Portal or DXP version
    Check the product version through the Lifer control panel (Control Panel > Configuration > System Information) or by inspecting the portal.properties or portal-ext.properties file
    Affected if The version matches 7.3, 7.4, 2023.q3.x, 2023.q4.x, or is >= 7.4.0 and < 7.4.3.110
  2. Locate the OpenAPI endpoint URL
    Common paths include /o/api or /api/openapi. Check your web server and application logs for any references to OpenAPI-related requests, or inspect the application's API documentation for endpoint paths
    Affected if OpenAPI endpoints exist and are routable in the application
  3. Test unauthenticated access to OpenAPI endpoint
    Send an HTTP GET request to the suspected OpenAPI endpoint URL (such as /o/api or /api/openapi) without providing any authentication credentials (no session cookie, no API key, no Basic Auth)
    Affected if The request returns HTTP 200 and displays API documentation, JSON, or YAML content without requiring login
  4. Attempt to download the OpenAPI YAML file
    Try accessing common OpenAPI YAML paths such as /o/api/openapi.yaml, /api/openapi.yaml, or /o/api/docs.yaml without authentication
    Affected if The YAML file downloads successfully and contains endpoint definitions, parameter schemas, and operational details without authentication

A user is affected if their Lifer Portal/DXP version falls within the listed ranges AND the OpenAPI endpoint or YAML file is accessible without any authentication.

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.110 or later
Fixed in 7.4.3.110
Interim mitigation

Configure web server or application-level access controls to restrict unauthorized access to OpenAPI endpoints and YAML files, limiting exposure to authenticated users only.

Recommended fix High confidence

LPortal: 7.4.3.110+ | DXP 2023.Q4.6+ or 2023.Q3.8+ or 7.4 update 93+ or 7.3 update 36+

  1. 1. Identify the current LPortal or DXP version by checking the control panel or the osgi/state directory
  2. 2. For Liferay Portal: upgrade from 7.4.0-7.4.3.109 to version 7.4.3.110 or later
  3. 3. For Liferay DXP: apply the relevant security patch or upgrade to a fixed release (2023.Q4.6+, 2023.Q3.8+, 7.4 update 93+, 7.3 update 36+)
  4. 4. After upgrade, verify the OpenAPI endpoint is properly protected by testing unauthenticated access attempts
  5. 5. Review user roles and permissions to ensure only authorized users can access sensitive API documentation
Caveat Standard upgrade precautions apply - test in staging environment first, backup database, review deprecated APIs in release notes

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

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-62256 — 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-62256 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