dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-62259

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-27
Fix available
A fix is available. Upgrade to 7.4.3.110 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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 older unsupported versions, 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 does not limit access to APIs before a user has verified their email address, which allows remote users to access and edit content via the API.

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

Limerick Portal and DXP versions fail to enforce email verification requirements before granting API access, allowing unverified users to access and modify content through exposed APIs. This represents an authentication bypass where the email verification step is not properly integrated into the API authorization flow.

MitigationImplement and enforce email verification checks in the API authentication layer to block unverified users from accessing or modifying content via APIs.

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.0= 7.1= 7.2= 7.3= 7.4= 2024.q3.1= 2024.q3.2= 2024.q3.3= 2024.q3.4
Liferay PortalApplication
Affected:< 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

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

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

  1. Identify installed Limerick Portal or DXP version
    Check the product version through the Limerick control panel (Control Panel > Configuration > System Information) or by inspecting the portal-ext.properties file for the version property, or by querying the Limerick API endpoint that returns system information
    Affected if The version matches: 7.0.x or earlier, 7.1.x, 7.2.x, 7.3.x, 7.4.x (any patch level below 7.4.3.110), 2024.q3.1, 2024.q3.2, 2024.q3.3, or 2024.q3.4
  2. Verify email verification settings in user management
    Navigate to Control Panel > Users > Users and verify the email verification requirement configuration. Check if the 'require verification' option is enabled in the authentication settings or portal-ext.properties (property: users.email.verification.required=true)
    Affected if Email verification is disabled or not enforced for user accounts in the system configuration
  3. Confirm API authentication layer does not enforce email verification
    Review the API authentication pipeline or OAuth configuration (typically in portal-ext.properties under oauth.* or api.auth.* settings) to determine if email verification status is checked before granting API token access
    Affected if The API authorization flow lacks a check to validate that the user's email has been verified before issuing access tokens
  4. Test API access with unverified user account
    Create a new user account without completing email verification, then attempt to call an API endpoint (such as the Headless Delivery API) using that user's credentials or token
    Affected if The API call succeeds and returns or modifies content despite the user not having verified their email address

You are affected if your Limerick Portal or DXP version falls within the listed vulnerable versions AND the system allows unverified users to successfully authenticate and perform operations through API endpoints without email verification being enforced in the authentication flow.

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

Implement and enforce email verification checks in the API authentication layer to block unverified users from accessing or modifying content via APIs.

Recommended fix High confidence

Lifer Portal 7.4.3.110+ / Lifer DXP 7.4 Update 93+ / Lifer DXP 7.3 Update 36+ / Lifer DXP 2023.Q4+

  1. 1. Identify the specific Lifer product and version currently installed (Portal or DXP, and the exact version/update number)
  2. 2. For Lifer Portal: Upgrade to version 7.4.3.110 or later
  3. 3. For Lifer DXP 7.4: Upgrade to Update 93 or later
  4. 4. For Lifer DXP 7.3: Upgrade to Update 36 or later
  5. 5. For Lifer DXP 2023.Q3: Upgrade to a version after 2023.Q4 (which contains the fix)
  6. 6. After upgrade, verify that unverified users can no longer access APIs via authorization testing
  7. 7. Review user roles and permissions to ensure the change does not break legitimate business workflows
Caveat Upgrading major versions may require compatibility testing with custom modules, themes, and integrations

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
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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