dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43789

MEDIUM · 5.3 CVSS v3.1 Published 2025-09-12
Fix available
A fix is available. Upgrade to 7.4.3.120 / 2024.Q1.10 or later.
See remediation →
62/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
JSON Web Services in Liferay Portal 7.4.0 through 7.4.3.119, and Liferay DXP 2024.Q1.1 through 2024.Q1.9, 7.4 GA through update 92 published to OSGi are registered and invoked directly as classes which allows Service Access Policies get executed.

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

JSON Web Services in Liferay Portal 7.4.0-7.4.3.119 and DXP 2024.Q1.1-2024.Q1.9 are registered and invoked directly as classes, which allows Service Access Policies to be executed. This class-based invocation bypasses intended security controls around the service layer.

MitigationUpgrade Liferay Portal to 7.4.3.120+ or DXP to the patched version beyond 2024.Q1.9. Review and validate Service Access Policies to ensure they are properly enforced for affected JSON web service endpoints.

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.10= 7.4
Liferay PortalApplication
Affected:>= 7.4.0, < 7.4.3.120

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 installed LiferPortal or DXP version
    Check the portal version in the LiferPortal admin console (Control Panel > Configuration > System Information) or examine the portal-impl.properties file in the installation. For DXP, check the digital experience platform version.
    Affected if Version is 7.4.0 through 7.4.3.119 for LiferPortal, or between 2024.Q1.1 and 2024.Q1.9 for DXP.
  2. Verify JSON Web Services are exposed
    Attempt to access the JSON web services endpoint at /api/jsonws or check the JSON ws configuration in the Control Panel under API > JSON Web Services. Confirm that JSON WS endpoints are listed as available.
    Affected if JSON web service endpoints are accessible and registered in the system.
  3. Inspect Service Access Policies configuration
    Navigate to Control Panel > Configuration > Service Access Policy (or equivalent in your version). Review the active policies to see which services are covered by access controls.
    Affected if Service Access Policies are defined but JSON web services may bypass these controls due to class-based invocation.
  4. Check for class-based JSON WS invocation patterns
    Review the JSON web service registry or examine the /api/jsonws/invoke endpoint to see how services are registered. Look for direct class references rather than service-based invocation.
    Affected if JSON WS services are registered and invoked as direct Java classes rather than through the service layer.

Your environment is affected if you run LiferPortal 7.4.0-7.4.3.119 or DXP 2024.Q1.1-2024.Q1.9 AND have JSON web services exposed with Service Access Policies that may not be properly enforced.

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.120 / 2024.Q1.10 or later
Fixed in 7.4.3.1202024.Q1.10
Interim mitigation

Upgrade Liferay Portal to 7.4.3.120+ or DXP to the patched version beyond 2024.Q1.9. Review and validate Service Access Policies to ensure they are properly enforced for affected JSON web service endpoints.

Recommended fix High confidence

Lifford Portal 7.4.3.120 or later / Lifford DXP 2024.Q1.10 or later

  1. 1. Identify the exact Lifford Portal or DXP version currently running using the Control Panel or Gogo shell command.
  2. 2. For Lifford Portal 7.4.x users: Schedule an upgrade to version 7.4.3.120 or later.
  3. 3. For Lifford DXP 2024.Q1.x users: Schedule an upgrade to version 2024.Q1.10 or later.
  4. 4. Before upgrading, perform a full backup of the database and documents/media repository.
  5. 5. Review the Lifford upgrade documentation for your specific version path.
  6. 6. Execute the upgrade in a staging environment first to verify compatibility with custom plugins and themes.
  7. 7. After upgrading, verify that JSON Web Services now correctly enforce Service Access Policies.
Caveat Standard Lifford upgrade considerations apply: test custom plugins/themes for 7.4.3 compatibility; review deprecated API usage

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 / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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