dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43763

MEDIUM · 6.5 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 7.4.3.132 / 2024.q1.21 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 exist in the Liferay Portal 7.4.0 through 7.4.3.131, and Liferay DXP 2024.Q4.0 through 2024.Q4.7, 2024.Q3.0 through 2024.Q3.13, 2024.Q2.0 through 2024.Q2.13 and 2024.Q1.1 through 2024.Q1.20 that affects custom object attachment fields. This flaw allows an attacker to manipulate the application into making unauthorized requests to other instances, creating new object entries that link to external resources.

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 server-side request forgery (SSRF) vulnerability in Lifford Portal/DXP's custom object attachment fields allows authenticated attackers to manipulate the application into making unauthorized HTTP requests to arbitrary internal or external resources and create object entries linking to those external resources.

MitigationApply vendor-supplied patches or upgrade to fixed Lifford Portal 7.4.3.132+ or DXP versions beyond the vulnerable releases (2024.Q4.8, 2024.Q3.14, 2024.Q2.14, 2024.Q1.21). Network segmentation and restrictive firewall rules can limit the impact of successful exploitation.

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.21>= 2024.q2.0, <= 2024.q2.13>= 2024.Q3.0, <= 2024.Q3.13>= 2024.q4.0, <= 2024.q4.7
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
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 the Lifford product and version
    Locate the installed Lifford Portal or DXP version through the administration interface (typically found in Control Panel > Configuration > Server Information) or check the portal's version file
    Affected if The product is Lifford Portal version < 7.4.3.132 or DXP version 2024.q1.1 through 2024.q1.20, 2024.q2.0 through 2024.q2.13, 2024.Q3.0 through 2024.Q3.13, or 2024.q4.0 through 2024.q4.7
  2. Verify custom object attachment fields are in use
    Check if custom objects with attachment field types have been created in the Lifford Object framework. Access Control Panel > Object > Objects and review the defined object definitions for any fields of type 'Attachment'
    Affected if Custom object definitions include attachment fields and those fields are accessible to authenticated users
  3. Confirm authenticated user access to object attachment functionality
    Review the roles and permissions assigned to users who can create or update object entries. Verify if any role grants permission to use custom object attachment fields
    Affected if Authenticated users with object entry creation/update permissions can interact with custom object attachment fields in the vulnerable version range

If the installed Lifford Portal is below 7.4.3.132 or DXP falls within any of the 2024.Q1-Q4 vulnerable ranges AND custom object attachment fields are configured with accessible entry creation, the environment is likely affected by this SSRF vulnerability.

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 or later
Fixed in 7.4.3.1322024.q1.21
Interim mitigation

Apply vendor-supplied patches or upgrade to fixed Lifford Portal 7.4.3.132+ or DXP versions beyond the vulnerable releases (2024.Q4.8, 2024.Q3.14, 2024.Q2.14, 2024.Q1.21). Network segmentation and restrictive firewall rules can limit the impact of successful exploitation.

Recommended fix High confidence

Upgrade to the appropriate fixed version: Lifford Portal 7.4.3.132, DXP 2024.Q1.21, DXP 2024.Q2.14, DXP 2024.Q3.14, or DXP 2024.Q4.8 (or later)

  1. 1. Identify the currently deployed Lifford Portal or DXP version by checking the control panel or osgi/state directory
  2. 2. For Lifford Portal 7.4.x: upgrade to version 7.4.3.132 or later
  3. 3. For DXP 2024.Q1.x: upgrade to version 2024.Q1.21 or later
  4. 4. For DXP 2024.Q2.x: upgrade to version 2024.Q2.14 or later
  5. 5. For DXP 2024.Q3.x: upgrade to version 2024.Q3.14 or later
  6. 6. For DXP 2024.Q4.x: upgrade to version 2024.Q4.8 or later
  7. 7. After upgrade, verify custom object attachment field functionality works correctly
  8. 8. Test that the SSRF vulnerability is remediated by attempting to use attachment fields with external URLs (in a test environment only)

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
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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