dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43747

MEDIUM · 6.5 CVSS v3.1 Published 2025-08-21
Fix available
A fix is available. Upgrade to 2025.Q2.4 or later.
See remediation →
74/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
A server-side request forgery (SSRF) vulnerability exists in the Liferay DXP 2025.Q2.0 through 2025.Q2.3 due to insecure domain validation on analytics.cloud.domain.allowed, allowing an attacker to perform requests by change the domain and bypassing the validation method, this insecure validation is not distinguishing between trusted subdomains and malicious domains.

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 · moderate confidence

Lifera DXP 2025.Q2.0-2025.Q2.3 contains an SSRF vulnerability in the analytics cloud feature. The analytics.cloud.domain.allowed setting uses insecure validation that fails to distinguish between trusted subdomains and malicious external domains, allowing attackers to bypass the validation and make the server perform arbitrary requests to attacker-controlled domains.

MitigationApply vendor patches when released; meanwhile, restrict or disable the analytics.cloud.domain.allowed configuration to minimize exposure, and monitor for unauthorized outbound requests.

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:>= 2025.Q2.0, < 2025.Q2.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
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 DXP version
    Check the installed Liferay DXP version. This is typically visible in the Control Panel under Configuration > Server Administration, or by inspecting the portal-version property in the system. Compare your version against the affected range: >= 2025.Q2.0 and < 2025.Q2.4
    Affected if The installed version falls within 2025.Q2.0 through 2025.Q2.3 inclusive
  2. Verify analytics cloud feature is configured
    Locate the analytics.cloud configuration in your Liferay instance. This is typically found in portal-ext.properties, system properties, or the Control Panel under Analytics Cloud settings. Determine whether the analytics cloud feature has been enabled.
    Affected if Analytics cloud feature is enabled and analytics.cloud.domain.allowed is configured with any domain values
  3. Inspect analytics.cloud.domain.allowed setting
    Examine the analytics.cloud.domain.allowed configuration value. This setting controls which domains the analytics cloud feature can make requests to. Review the list of allowed domains for any entries that could allow bypass to untrusted external domains.
    Affected if The analytics.cloud.domain.allowed setting contains domain patterns that do not properly restrict to internal or trusted subdomains only, or contains wildcards that could match external domains
  4. Review outbound network activity
    Monitor server logs and network traffic for outbound requests originating from the Liferay server to domains that are not your trusted internal domains. Check for any unexpected HTTP/HTTPS connections that could indicate exploitation of the SSRF vulnerability.
    Affected if Unusual or unauthorized outbound requests to external domains are observed from the server

You are affected if your Liferay DXP version is between 2025.Q2.0 and 2025.Q2.3 inclusive AND the analytics cloud feature is enabled with the analytics.cloud.domain.allowed configuration containing domains that can be bypassed for SSRF attacks.

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 2025.Q2.4 or later
Fixed in 2025.Q2.4
Interim mitigation

Apply vendor patches when released; meanwhile, restrict or disable the analytics.cloud.domain.allowed configuration to minimize exposure, and monitor for unauthorized outbound requests.

Recommended fix High confidence

2025.Q2.4

  1. Upgrade Liferay Digital Experience Platform from any 2025.Q2.0-2025.Q2.3 version to version 2025.Q2.4 or later

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