dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43792

MEDIUM · 5.3 CVSS v3.1 Published 2025-09-15
Fix available
A fix is available. Upgrade to 7.3 / 7.4.3.106 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable 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
Remote staging in Liferay Portal 7.4.0 through 7.4.3.105, and older unsupported versions, and Liferay DXP 2023.Q4.0, 2023.Q3.1 through 2023.Q3.4, 7.4 GA through update 92, 7.3 GA through update 35, and older unsupported versions does not properly obtain the remote address of the live site from the database which, which allows remote authenticated users to exfiltrate data to an attacker controlled server (i.e., a fake “live site”) via the _com_liferay_exportimport_web_portlet_ExportImportPortlet_remoteAddress and _com_liferay_exportimport_web_portlet_ExportImportPortlet_remotePort parameters. To successfully exploit this vulnerability, an attacker must also successfully obtain the staging server’s shared secret and add the attacker controlled server to the staging server’s whitelist.

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

Liferit's remote staging feature fails to properly retrieve and validate the remote address of the live site from the database. This allows an authenticated attacker who has obtained the staging server's shared secret to add an attacker-controlled server to the staging whitelist and exfiltrate data through the ExportImportPortlet using the remoteAddress and remotePort parameters.

MitigationUpgrade to the patched Liferit version. Immediately rotate staging shared secrets, audit the staging server whitelist for unauthorized entries, and restrict access to staging configuration to trusted administrators only.

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:< 7.3>= 2023.q3.1, < 2023.q3.5= 7.3= 7.4= 2023.q4.0
Liferay PortalApplication
Affected:< 7.4.3.106

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/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. Check Liferit portal version
    Access the Liferit Control Panel > Configuration > Server Administration > Overview, or inspect the portal-ext.properties file for the version property, or query the OSGi console for bundle version com.liferit.portal
    Affected if The installed version is Liferit Portal < 7.4.3.106, or Liferit DXP < 7.3, or any version from 2023.q3.1 to 2023.q3.4, or 2023.q4.0, or 7.3, or 7.4 (specific builds within these branches)
  2. Verify remote staging is enabled
    Navigate to Liferit Control Panel > Configuration > Staging > Remote Staging, or inspect the database table StagingConfiguration for rows where remoteStagingEnabled = true
    Affected if Remote staging is currently enabled on the system
  3. Confirm ExportImportPortlet is accessible
    Access the ExportImportPortlet via the Liferit Control Panel at Ports > Export Import, or check the OSGi configuration for com.liferit.exportimport.portlet.ExportImportPortlet to verify it is registered and not disabled
    Affected if The ExportImportPortlet is active and accessible to authenticated users with staging permissions
  4. Inspect staging server whitelist
    Query the database table RemoteStagingGroupGroupRel or inspect the staging configuration JSON at Liferit Control Panel > Configuration > Staging > Remote Staging > Servers whitelist
    Affected if The whitelist contains servers that were not added by a trusted administrator, or contains any server with an unexpected remoteAddress or remotePort value
  5. Verify staging shared secret configuration
    Check the portal-ext.properties for the property staging.shared.secret, or inspect the encrypted value in the database table StagingConfiguration for the sharedSecret field
    Affected if A staging shared secret is configured and active (the attacker needs this secret to exploit the vulnerability)

A user is affected if they are running any of the listed vulnerable Liferit versions with remote staging enabled and the ExportImportPortlet accessible, combined with an active staging shared secret.

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.3 / 7.4.3.106 / 2023.q3.5 or later
Fixed in 7.37.4.3.1062023.q3.5
Interim mitigation

Upgrade to the patched Liferit version. Immediately rotate staging shared secrets, audit the staging server whitelist for unauthorized entries, and restrict access to staging configuration to trusted administrators only.

Recommended fix High confidence

LPortal 7.4.3.106+ / DXP 7.4 Update 93+ / DXP 7.3 Update 36+ / DXP 2023.Q3.5+

  1. 1. Back up your current Liferay Portal/DXP database and configuration files before proceeding with any upgrade.
  2. 2. Identify your current LPortal/DXP version using the Control Panel > Server Administration > Summary.
  3. 3. For Liferay Portal 7.4.x users: Upgrade to LPortal 7.4.3.106 or later.
  4. 4. For Liferay DXP 7.4 users: Apply DXP 7.4 Update 93 or later (which includes the fix for 7.4.3.106).
  5. 5. For Lifer DXP 7.3 users: Apply DXP 7.3 Update 36 or later.
  6. 6. For Lifer DXP 2023.Q3.x users: Upgrade to DXP 2023.Q3.5 or later.
  7. 7. After upgrade, verify the Remote Staging configuration at: Control Panel > Publishing > Staging > Remote Staging.
  8. 8. Confirm the remote address is now properly obtained from the database configuration rather than user-supplied parameters.
Caveat Review custom staging configurations and ensure compatibility with the new staging architecture; test remote staging functionality in a non-production environment first.

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 / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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