dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43770

MEDIUM · 6.1 CVSS v3.1 Published 2025-08-23
Fix available
A fix is available. Upgrade to 7.4.3.132 / 2024.Q1.13 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.3, 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 referer or FORWARD_URL using %00 in those parameters.

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-7.4.3.131 and L DXP allows unauthenticated remote attackers to inject JavaScript via the referer header or FORWARD_URL parameter by using a null byte (%00) to bypass input filtering. The malicious payload is reflected in the HTTP response without proper sanitization.

MitigationApply the vendor patch for the affected Lifer version (upgrade to 7.4.3.132+, or the appropriate DXP update that includes the fix). Alternatively, implement input validation to filter null bytes (%00) and encode output in the referer and FORWARD_URL handling code.

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.13>= 2024.q2.0, <= 2024.q2.13>= 2024.Q3.1, <= 2024.Q3.12>= 2024.Q4.0, < 2024.Q4.4= 7.4
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 LPortal or DXP version
    Locate the version file or check the control panel: typically in {LIFERAY_HOME}/portal-impl/build.properties or via the Control Panel > Configuration > Server Administration > Product Information
    Affected if The version displayed is 7.4.0 through 7.4.3.131 for LPortal, or falls within the DXP ranges: 2024.Q1.1-2024.Q1.12, 2024.Q2.0-2024.Q2.13, 2024.Q3.1-2024.Q3.12, 2024.Q4.0-2024.Q3, or version 7.4
  2. Confirm FORWARD_URL parameter handling is in use
    Inspect HTTP requests to the portal looking for the FORWARD_URL parameter in URLs or check web.xml for any filters that process this parameter
    Affected if The FORWARD_URL parameter is accepted and reflected in responses without null byte filtering
  3. Check referer header processing
    Review server logs or web server configuration to see if the referer header value is used in any dynamic response content
    Affected if The application echoes the referer header value in HTTP responses without sanitization

A user is affected if they are running LPortal 7.4.0-7.4.3.131 or any of the specified DXP versions AND the FORWARD_URL parameter or referer header can be reflected in responses to unauthenticated users.

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.13 / 2024.Q4.4 or later
Fixed in 7.4.3.1322024.Q1.132024.Q4.4
Interim mitigation

Apply the vendor patch for the affected Lifer version (upgrade to 7.4.3.132+, or the appropriate DXP update that includes the fix). Alternatively, implement input validation to filter null bytes (%00) and encode output in the referer and FORWARD_URL handling code.

Recommended fix High confidence

Lifera Portal 7.4.3.132 or later; DXP 2024.Q1.13, 2024.Q2.14, 2024.Q3.13, or 2024.Q4.4 (whichever train applies)

  1. Identify your current Liferous Portal or DXP version from the Liferay Server Control Panel or version.properties file
  2. For Liferay Portal 7.4.x users: Upgrade to version 7.4.3.132 or later
  3. For Liferay DXP 2024.Q1 customers: Upgrade to version 2024.Q1.13 or later
  4. For Liferax DXP 2024.Q2 customers: Upgrade to version 2024.Q2.14 or later
  5. For Liferax DXP 2024.Q3 customers: Upgrade to version 2024.Q3.13 or later
  6. For Liferax DXP 2024.Q4 customers: Upgrade to version 2024.Q4.4 or later
  7. After upgrade, verify the referer and FORWARD_URL parameters are properly sanitized and no longer accept %00 for XSS injection
  8. Test that the upgrade does not break existing customizations in your environment
Caveat Standard Liferay upgrade considerations apply - review breaking changes in the upgrade guide for your specific version jump, test custom portlets and themes 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
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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