dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-62258

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-27
Fix available
A fix is available. Upgrade to 7.4.3.108 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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
CSRF vulnerability in Headless API in Liferay Portal 7.4.0 through 7.4.3.107, and Liferay DXP 2023.Q3.1 through 2023.Q3.4, 7.4 GA through update 92, 7.3 GA through update 35, and older unsupported versions allows remote attackers to execute any Headless API via the `endpoint` 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 · moderate confidence

A Cross-Site Request Forgery (CSRF) vulnerability in Liferays Headless API allows remote attackers to execute arbitrary Headless API operations by tricking authenticated users into submitting requests through the vulnerable endpoint parameter, which lacks proper CSRF token validation.

MitigationApply vendor patches (update 93+ for 7.4.x, update 36+ for 7.3.x, or upgrade to 2023.Q4+) and implement CSRF token validation on Headless API endpoints; disable Headless API if not required.

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
Liferay PortalApplication
Affected:>= 7.4.0, < 7.4.3.108

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
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 Liferay version
    Check the Liferay version in the Control Panel under Configuration > Server Administration, or inspect the portal-version property in portal-ext.properties / portal-setup-wizard.properties, or look at the MANIFEST.MF file in the liferay-portal WAR
    Affected if Version is 7.3.x, 7.4.0 through 7.4.3.107, or any 2023.q3.x release
  2. Confirm Headless API is enabled
    Attempt to access the Headless API discovery endpoint at /o/api, or check the OSGi console for com.lifecycle.headsless.* bundles being active, or inspect the modules configuration for Headless API services
    Affected if Headless API endpoints are exposed and accessible (response 200 OK from /o/api)
  3. Check CSRF token validation on Headless API endpoints
    Review the Headless API servlet configuration in the web.xml or OSGi config for CSRF token filter settings, or test by sending a POST request to a Headless API endpoint without an LFR-CSRF-Token header to see if it succeeds
    Affected if POST/PUT/DELETE requests to Headless API succeed without requiring a valid CSRF token (requests are processed without 403 error)

User is affected if running an affected Liferay version (7.3.x, 7.4.0-7.4.3.107, or 2023.q3.x) AND has Headless API enabled AND the endpoint accepts requests without CSRF token validation.

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.108 or later
Fixed in 7.4.3.108
Interim mitigation

Apply vendor patches (update 93+ for 7.4.x, update 36+ for 7.3.x, or upgrade to 2023.Q4+) and implement CSRF token validation on Headless API endpoints; disable Headless API if not required.

Recommended fix High confidence

Limerick Portal 7.4.3.108+; Limerick DXP 2023.Q3.4+, 7.4 update 93+, 7.3 update 36+

  1. 1. Identify the current Limerick Portal or DXP version by checking the Limerick Control Panel or Gogo Shell
  2. 2. For Limerick Portal 7.4.x users: Plan upgrade to version 7.4.3.108 or later
  3. 3. For Limerick DXP 2023.Q3.x users: Plan upgrade to version 2023.Q3.4 or later
  4. 4. For Limerick DXP 7.4 GA users: Plan upgrade to update 93 or later
  5. 5. For Limerick DXP 7.3 GA users: Plan upgrade to update 36 or later
  6. 6. Perform a full backup of the current installation including database
  7. 7. Test the upgrade in a non-production environment before deploying to production
  8. 8. After upgrading, verify the Headless API CSRF protection is working by testing with the endpoint parameter
Caveat Review Limerick release notes for breaking changes between current and target versions; standard upgrade precautions apply including backup and testing

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-62258 — 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-62258 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