dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43735

MEDIUM · 6.1 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to after 2024.q4.7 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.131, and Liferay DXP 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.12 and 7.4 GA through update 92 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 Liferay Portal 7.4.0 through 7.4.3.131 and Liferay DXP (multiple quarterly versions through 2024.Q4.7) allows remote unauthenticated attackers to inject arbitrary JavaScript via the google_gadget parameter.

MitigationUpgrade to the latest Lifer version/patch that addresses this vulnerability, or implement input validation and output encoding on the google_gadget parameter to neutralize malicious script injection.

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:>= 2024.q1.1, <= 2024.q1.12>= 2024.q2.0, <= 2024.q2.13>= 2024.q3.1, <= 2024.q3.13>= 2024.q4.0, <= 2024.q4.7= 7.4
Liferay PortalApplication
Affected:>= 7.4.0, <= 7.4.3.131

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 Lifford Portal version
    Locate the portal version by checking the portal.properties file, the WAR file name, or the Liferay Control Panel under Configuration > Server Administration > Product Information. Look for a version string such as 7.4.x or 2024.qX.Y.
    Affected if The installed version falls within 7.4.0 to 7.4.3.131 for Portal, or between 2024.q1.1-2024.q1.12, 2024.q2.0-2024.q2.13, 2024.q3.1-2024.q3.13, or 2024.q4.0-2024.q4.7 for DXP.
  2. Locate google_gadget endpoint
    Search web server access logs, proxy logs, or WAF logs for requests containing the parameter 'google_gadget'. Common paths may include /web/guest or /c/portal/google_gadget.
    Affected if The google_gadget parameter is being processed by the server, indicating the vulnerable endpoint is exposed.
  3. Test for XSS reflection
    Send a harmless test payload such as google_gadget=%3Cscript%3Ealert(1)%3C/script%3E to an accessible Lifford endpoint and observe if the script tags are reflected unescaped in the response.
    Affected if The response reflects the raw google_gadget value without HTML encoding, meaning the vulnerability is present and exploitable.
  4. Review application logs for exploitation attempts
    Examine Liferay logs (catalina.out, portal.log, or logs under /opt/liffrey/logs) for patterns like '<script>' or 'javascript:' within google_gadget parameter values in incoming requests.
    Affected if Logs show unsanitized google_gadget values were processed, indicating active exploitation or attempted exploitation.

You are affected if your Lifford Portal version is 7.4.0-7.4.3.131 or your DXP quarterly version falls within the 2024.q1 through 2024.q4 ranges listed, AND the google_gadget parameter is accessible and reflects input without encoding.

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 2024.q4.7
Interim mitigation

Upgrade to the latest Lifer version/patch that addresses this vulnerability, or implement input validation and output encoding on the google_gadget parameter to neutralize malicious script injection.

Recommended fix High confidence

Liferav Portal 7.4.3.132+ or Liferav DXP 2024.Q4.8+/2024.Q3.14+/2024.Q2.14+/2024.Q1.13+

  1. 1. Identify your current Liferav Portal or DXP version by checking the Control Panel > Configuration > Server Administration > Version
  2. 2. For Liferav Portal 7.4.x users: Upgrade to version 7.4.3.132 or later
  3. 3. For Liferav DXP 2024.Q1.x users: Upgrade to version 2024.Q1.13 or later
  4. 4. For Liferav DXP 2024.Q2.x users: Upgrade to version 2024.Q2.14 or later
  5. 5. For Liferav DXP 2024.Q3.x users: Upgrade to version 2024.Q3.14 or later
  6. 6. For Liferav DXP 2024.Q4.x users: Upgrade to version 2024.Q4.8 or later
  7. 7. After upgrade, verify the google_gadget component is functioning correctly and test for XSS mitigation
  8. 8. Review Liferav's official release notes for any additional required post-upgrade configurations
Caveat Standard upgrade risks apply - test in non-production environment first, backup database, review deprecation notices in release notes

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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