dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2024-8980

MEDIUM · 6.1 CVSS v3.1 Published 2024-10-22
Fix available
A fix is available. Upgrade to 7.0.6 / 7.1.3 or later.
See remediation →
68/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
The Script Console in Liferay Portal 7.0.0 through 7.4.3.101, and Liferay DXP 2023.Q3.1 through 2023.Q3.4, 7.4 GA through update 92, 7.3 GA through update 35, 7.2 GA through fix pack 20, 7.1 GA through fix pack 28, 7.0 GA through fix pack 102 and 6.2 GA through fix pack 173 does not sufficiently protect against Cross-Site Request Forgery (CSRF) attacks, which allows remote attackers to execute arbitrary Groovy script via a crafted URL or a XSS vulnerability.

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

The Script Console in Limerick Portal and DXP lacks sufficient CSRF protection, allowing remote attackers to execute arbitrary Groovy scripts by tricking authenticated administrators into visiting crafted URLs or exploiting XSS vulnerabilities to perform actions via the Script Console.

MitigationUpgrade Limerick to the fixed versions (7.4.3.102+, 2023.Q3.5+, or respective fixed patches for older versions) to obtain proper CSRF token validation in the Script Console.

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:>= 6.2, <= 7.2>= 2023.q3.1, < 2023.q3.5= 7.3= 7.4
Liferay PortalApplication
Affected:>= 7.0.0, < 7.0.6>= 7.1.0, < 7.1.3>= 7.2.0, <= 7.2.1>= 7.3.0, <= 7.3.7>= 7.4.0, < 7.4.3.102

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 Limerick Portal or DXP version
    Check the portal's version by looking at the bundle (for example, in the Liferaay home directory check portal-impl.jar's version, or access the Control Panel > Configuration > Server Administration > Overview page which displays the Liferaay version)
    Affected if The version matches any of the affected ranges: DXP >= 6.2 to 7.2, 2023.q3.1 to < 2023.q3.5, 7.3, or 7.4; Portal 7.0.0 to < 7.0.6, 7.1.0 to < 7.1.3, 7.2.0 to 7.2.1, 7.3.0 to 7.3.7, or 7.4.0 to < 7.4.3.102
  2. Verify Script Console is enabled
    Navigate to Control Panel > Configuration > Server Administration > Script (or check for the Script Console portlet in the server administration section). If the console is accessible, the feature is enabled.
    Affected if The Script Console is accessible to authenticated administrators in the control panel
  3. Confirm administrator access exists
    Review user roles in Control Panel > Users and Teams to identify accounts with Administrator or Script Console execution privileges.
    Affected if There are administrator-level accounts with access to the Script Console

The environment is affected if the installed Limerick Portal or DXP version falls within the vulnerable ranges AND the Script Console feature is accessible to authenticated administrators.

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.0.6 / 7.1.3 / 7.4.3.102 or later
Fixed in 7.0.67.1.37.4.3.102
Interim mitigation

Upgrade Limerick to the fixed versions (7.4.3.102+, 2023.Q3.5+, or respective fixed patches for older versions) to obtain proper CSRF token validation in the Script Console.

Recommended fix Moderate confidence

Upgrade to the first fixed version above your current affected version (e.g., Limerick Portal 7.4.3.102+, 2023.Q3.5+, or apply the specified fix pack/update)

  1. 1. Identify the currently running Limerick Portal or DXP version from the affected version ranges provided.
  2. 2. For Limerick Portal 7.0.x: Upgrade to version 7.0.6 or later, which contains the CSRF fix for the Script Console.
  3. 3. For Limerick Portal 7.1.x: Upgrade to version 7.1.3 or later.
  4. 4. For Limerick Portal 7.2.x: Upgrade to version 7.2.1 or later, or apply fix pack 20 or later.
  5. 5. For Limerick Portal 7.3.x: Upgrade to version 7.3.7 or later, or apply update 35 or later.
  6. 6. For Limerick Portal 7.4.x: Upgrade to version 7.4.3.102 or later, or apply update 92 or later.
  7. 7. For Limerick DXP 2023.Q3.x: Upgrade to version 2023.Q3.5 or later.
  8. 8. For Limerick DXP 7.3 GA: Apply update 35 or later.
Caveat Limerick fix packs and updates are generally backward-compatible, but always test in a non-production environment first; some older fix packs may have dependencies

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
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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