dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-62249

MEDIUM · 6.1 CVSS v3.1 Published 2025-10-21
Fix available
A fix is available. Upgrade to 7.4.3.132 / 2024.q1.21 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
A reflected cross-site scripting (XSS) vulnerability in the Liferay Portal 7.4.0 through 7.4.3.132, and Liferay DXP 2025.Q3.0 through 2025.Q3.2, 2025.Q2.0 through 2025.Q2.12, 2025.Q1.0 through 2025.Q1.17, 2024.Q4.0 through 2024.Q4.7, 2024.Q3.1 through 2024.Q3.13, 2024.Q2.0 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.20, and 2023.Q4.0 through 2023.Q4.10 allows an remote non-authenticated attacker to inject JavaScript into the google_gadget.

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

A reflected cross-site scripting (XSS) vulnerability in Limerick Portal and DXP allows unauthenticated remote attackers to inject malicious JavaScript via the google_gadget parameter. The vulnerability stems from insufficient input validation or output encoding when processing this parameter.

MitigationApply proper input validation and output encoding to the google_gadget parameter, or disable the google_gadget functionality 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:>= 2023.q4.0, <= 2023.q4.10>= 2024.q1.1, < 2024.q1.21>= 2024.q2.0, <= 2024.q2.13>= 2024.q3.1, <= 2024.q3.13>= 2025.q1.0, < 2025.q1.18>= 2025.q2.0, <= 2025.q2.12>= 2025.q3.0, < 2025.q3.3
Liferay PortalApplication
Affected:>= 7.4.0, < 7.4.3.132

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 Liferay product and version
    Check the portal's version via the Control Panel > Configuration > Server Administration > Version, or inspect the liferay-portal.properties or manifest.mf file in the installation directory
    Affected if The installed version falls within any of these ranges: LDP 2023.q4.0-2023.q4.10, 2024.q1.1-2024.q1.21, 2024.q2.0-2024.q2.13, 2024.q3.1-2024.q3.13, 2025.q1.0-2025.q1.18, 2025.q2.0-2025.q2.12, 2025.q3.0-2025.q3.3; or Liferay Portal 7.4.0 to <7.4.3.132
  2. Determine if google_gadget feature is enabled
    Search the portal-ext.properties, portal-setup-wizard.properties, or system-ext.properties files for the property 'google.gadget.enabled' and check its value, or inspect the Google Gadget configuration in the Control Panel under Apps > App Manager
    Affected if The google_gadget feature is enabled (property set to true or not explicitly disabled)
  3. Test for vulnerable parameter reflection
    Send a GET request to any portal page with the parameter 'google_gadget' set to a test payload such as '<script>alert(1)</script>' and observe if the parameter value is reflected unescaped in the response
    Affected if The parameter value is reflected in the HTML response without proper encoding or validation

You are affected if your Liferay Portal or DXP version is within the affected ranges AND the google_gadget feature is enabled, which allows the vulnerable parameter to be processed.

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.132 / 2024.q1.21 / 2025.q1.18 or later
Fixed in 7.4.3.1322024.q1.212025.q1.18
Interim mitigation

Apply proper input validation and output encoding to the google_gadget parameter, or disable the google_gadget functionality if not required.

Recommended fix High confidence

Upgrade to the first fixed release above your current version (e.g., 7.4.3.132 for Portal, or the next quarterly patch for DXP)

  1. 1. Identify your current Lifter Portal or DXP version from the control panel or version file
  2. 2. For Lelter Portal 7.4.x users: Upgrade to version 7.4.3.132 or later
  3. 3. For DXP 2023.Q4.x users: Upgrade to version 2023.Q4.11 or later
  4. 4. For DXP 2024.Q1.x users: Upgrade to version 2024.Q1.21 or later
  5. 5. For DXP 2024.Q2.x users: Upgrade to version 2024.Q2.14 or later
  6. 6. For DXP 2024.Q3.x users: Upgrade to version 2024.Q3.14 or later
  7. 7. For DXP 2024.Q4.x users: Upgrade to version 2024.Q4.8 or later
  8. 8. For DXP 2025.Q1.x users: Upgrade to version 2025.Q1.18 or later
Caveat Review Lelter release notes for your target version as minor/major upgrades may include breaking changes; test in staging environment before production deployment

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