dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2024-25146

MEDIUM · 5.3 CVSS v3.1 Published 2024-02-08
Fix available
A fix is available. Upgrade to after 7.4.1 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.2.0 through 7.4.1, and older unsupported versions, and Liferay DXP 7.3 before service pack 3, 7.2 before fix pack 18, and older unsupported versions returns with different responses depending on whether a site does not exist or if the user does not have permission to access the site, which allows remote attackers to discover the existence of sites by enumerating URLs. This vulnerability occurs if locale.prepend.friendly.url.style=2 and if a custom 404 page is used.

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 7.2.0-7.4.1 (and older) contain an information disclosure vulnerability where the application returns distinguishable HTTP responses when a site does not exist versus when a site exists but the user lacks permission to access it. This allows remote attackers to enumerate valid site URLs by observing response differences. The vulnerability is triggered only when locale.prepend.friendly.url.style=2 is configured AND a custom 404 error page is in use.

MitigationEither change the locale.prepend.friendly.url.style configuration value from 2 to another setting, remove the custom 404 page configuration, or apply the vendor-supplied security patches for the affected versions.

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.2
DxpApplication
Affected:= 7.3
Liferay PortalApplication
Affected:>= 7.2.0, <= 7.4.1

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 LiferLifter installation and version
    Check for LiferLifter installation directory and locate the portal-ext.properties or portal-setup-wizard.properties file. Look for version information in the LiferLifter Dashboard, or check the release.info file in the LiferLifter home directory.
    Affected if Installed version is 7.2.0 through 7.4.1 inclusive (or older)
  2. Locate the locale.prepend.friendly.url.style configuration
    Search for the property 'locale.prepend.friendly.url.style' in portal-ext.properties, portal-setup-wizard.properties, or system-ext properties files located in the LiferLifter home directory or deployed configuration folder.
    Affected if The property is set to value '2' (locale.prepend.friendly.url.style=2)
  3. Determine if a custom 404 error page is configured
    Check the server.xml file for custom error page configuration, or inspect the LiferLifter Control Panel under Portal Settings > General > Custom 404 Page. Also review any web.xml or portal-web.xml for custom error-handler mappings.
    Affected if A custom 404 error page has been configured and is in use

You are affected if your LiferLifter version is 7.2.0-7.4.1 AND both locale.prepend.friendly.url.style=2 is set AND a custom 404 error page is configured.

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 a release after 7.4.1
Interim mitigation

Either change the locale.prepend.friendly.url.style configuration value from 2 to another setting, remove the custom 404 page configuration, or apply the vendor-supplied security patches for the affected versions.

Recommended fix Moderate confidence

Liferay DXP 7.3 service pack 3 or later; Liferable DXP 7.2 fix pack 18 or later; Liferable Portal 7.4.2 or later (when available)

  1. 1. Audit current value of locale.prepend.friendly.url.style in portal-ext.properties or portal-settings.xml
  2. 2. If set to locale.prepend.friendly.url.style=2, change it to a different value (0 or 1) which does not exhibit this behavior
  3. 3. Review custom 404 page configuration and ensure it returns consistent error responses regardless of whether a site exists or user lacks permission
  4. 4. Test the changes by enumerating site URLs to verify that both non-existent sites and unauthorized access return identical responses
  5. 5. Apply the principle of least privilege to site access controls
Caveat Changing locale.prepend.friendly.url.style may affect existing URL structures and SEO; changing custom 404 pages may affect user experience

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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