dbcve.org
Liferay PortalApplication · Liferay

CVE-2024-26267

MEDIUM · 5.3 CVSS v3.1 Published 2024-02-20
Fix available
A fix is available. Upgrade to 7.2 / 7.4.3.26 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
In Liferay Portal 7.2.0 through 7.4.3.25, and older unsupported versions, and Liferay DXP 7.4 before update 26, 7.3 before update 5, 7.2 before fix pack 19, and older unsupported versions the default value of the portal property `http.header.version.verbosity` is set to `full`, which allows remote attackers to easily identify the version of the application that is running and the vulnerabilities that affect that version via 'Liferay-Portal` response header.

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

In Limerick Portal 7.2.0-7.4.3.25 and Limerick DXP (7.4 < update 26, 7.3 < update 5, 7.2 < fix pack 19), the portal property `http.header.version.verbosity` defaults to 'full', causing the `Lifera-Portal` HTTP response header to expose the exact version number. This version information allows remote attackers to fingerprint the application and identify known vulnerabilities affecting that specific version.

MitigationSet the portal property `http.header.version.verbosity` to a less verbose value (such as 'partial' or 'none') in the portal-ext.properties or portal-setup-wizard.properties file, then restart the application server.

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
Liferay PortalApplication
Affected:<= 7.3.7>= 7.4.0, < 7.4.3.26
Digital Experience PlatformApplication
Affected:< 7.2= 7.2= 7.3= 7.4

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. Check for version-exposing HTTP response header
    Send an HTTP request to the portal (e.g., curl -I https://yourportal.example.com) and inspect the response headers for a header named 'Lifera-Portal'
    Affected if The 'Lifera-Portal' header is present and contains a full version number (such as 7.4.3.25 or similar)
  2. Verify the http.header.version.verbosity property setting
    Inspect the portal-ext.properties or portal-setup-wizard.properties file (typically in the Liferay home directory or application server config) and look for the property 'http.header.version.verbosity'
    Affected if The property is set to 'full' or is absent (defaults to 'full'), meaning version information is fully exposed
  3. Determine the installed Liferay Portal version
    Check the portal's version by inspecting the manifest file, the Liferay Dashboard (if accessible), or the 'Lifera-Portal' header value itself
    Affected if The installed version falls within <= 7.3.7, >= 7.4.0 and < 7.4.3.26, or is any version of Liferay DXP (7.2, 7.3, or 7.4) prior to their respective updates

You are affected if the 'Lifera-Portal' header reveals the full version number and your installation matches the affected version ranges, with the property set to 'full' or left at default.

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.2 / 7.4.3.26 or later
Fixed in 7.27.4.3.26
Interim mitigation

Set the portal property `http.header.version.verbosity` to a less verbose value (such as 'partial' or 'none') in the portal-ext.properties or portal-setup-wizard.properties file, then restart the application server.

Recommended fix High confidence

Liferay Portal 7.4.3.26 / DXP 7.4 Update 26 / DXP 7.3 Update 5 / DXP 7.2 Fix Pack 19

  1. 1. Identify the exact Liferay product and version currently running (Portal or DXP, and version number)
  2. 2. For Liferay Portal 7.4.x: Upgrade to version 7.4.3.26 or later
  3. 3. For Liferay DXP 7.4: Apply Update 26 or later
  4. 4. For Liferay DXP 7.3: Apply Update 5 or later
  5. 5. For Liferay DXP 7.2: Apply Fix Pack 19 or later
  6. 6. After upgrade, verify the fix by making a request and confirming the 'Liferay-Portal' header no longer exposes full version information
  7. 7. Alternatively or additionally, set the portal property 'http.header.version.verbosity' to 'minimal' or 'none' in portal-ext.properties or portal-setup-wizard.properties

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

Fix this in Liferay Portal Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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