Digital Experience PlatformApplication · Liferay

CVE-2025-43773

CRITICAL · 9.1 CVSS v3.1 Published 2025-08-29

Fix available

A fix is available. Upgrade to 2024.Q1.19 / 2025.Q1.15 or later.

See remediation →

100/100

Remediation priority · Urgent

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Liferay Portal 7.4.0 through 7.4.3.132, and Liferay DXP 2025.Q2.0, 2025.Q1.0 through 2025.Q1.14, 2024.Q4.0 through 2024.Q4.7, 2024.Q3.0 through 2024.Q3.13, 2024.Q2.0 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.18 and 7.4 GA through update 92 has a security vulnerability that allowing for improper access through the expandoTableLocalService.

Technical summary

dbcve analysis · moderate confidence

Lifter Portal and DXP contain an improper access control vulnerability in the expandoTableLocalService that allows unauthorized access to custom field (expando) data. This service-level access control flaw enables authenticated users to potentially read or modify custom attribute data beyond their authorized scope.

MitigationApply the appropriate Liferay patch or upgrade to a fixed version beyond 7.4.3.132 for Portal or beyond the listed Q1/Q2 2025 versions for DXP.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Digital Experience PlatformApplication

Affected:>= 2024.Q1.1, < 2024.Q1.19>= 2024.q2.0, <= 2024.q2.13>= 2024.Q3.0, <= 2024.Q3.13>= 2024.q4.0, <= 2024.q4.7>= 2025.Q1.0, < 2025.Q1.15= 7.4= 2025.q2.0

Liferay PortalApplication

Affected:>= 7.4.0, <= 7.4.3.132

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify installed Liferays version

Access Liferays Control Panel > Configuration > Server Administration > Version, or check the startup log file (typically catalina.out) for the version string displayed at startup.

Affected if The version is 7.4.0 through 7.4.3.132 for Liferays Portal, or within any of these DXP ranges: 2024.Q1.1 to 2024.Q1.19, 2024.Q2.0 to 2024.Q2.13, 2024.Q3.0 to 2024.Q3.13, 2024.Q4.0 to 2024.Q4.7, 2025.Q1.0 to 2025.Q1.14, or exactly 2025.Q2.0.
Confirm expando/custom attributes feature is in use

Navigate to Control Panel > Configuration > Custom Fields, or query the database table EXPANDOTABLE for any records. If no custom fields are defined, the attack surface is reduced.

Affected if Any custom attributes or expando tables are defined in the system.
Verify network accessibility of Liferays API endpoints

Attempt a GET request to the Liferays API base URL (typically /o/api) without credentials. The vulnerability allows unauthenticated access, so exposed API endpoints indicate potential exploitability.

Affected if The Liferays REST/API endpoints are accessible from the network without authentication.
Inspect expandoTableLocalService for unexpected access

Review server access logs for calls to endpoints containing 'expando' or 'expandotablelocalservice'. Check for requests from unauthorized IP addresses or unusual query patterns against expando tables.

Affected if There are API calls to expando-related endpoints originating from unexpected sources or without valid session tokens.

Your environment is affected if the installed Liferays version falls within the affected ranges AND the expando/custom attributes feature is enabled AND the API is network-accessible, allowing unauthenticated attackers to potentially read or modify custom attribute data.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 2024.Q1.19 / 2025.Q1.15 or later

Fixed in 2024.Q1.192025.Q1.15

Interim mitigation

Apply the appropriate Liferay patch or upgrade to a fixed version beyond 7.4.3.132 for Portal or beyond the listed Q1/Q2 2025 versions for DXP.

Recommended fix Moderate confidence

Linerick DXP 2024.Q1.19+ / 2024.Q2.14+ / 2024.Q3.14+ / 2024.Q4.8+ or Linerick Portal 7.4.3.133+

1. Identify the currently installed Limerick DXP or Portal version using the Control Panel or system information.
2. For DXP 2024.Q1.x installations: Upgrade to version 2024.Q1.19 or later to resolve the missing authorization vulnerability in expandoTableLocalService.
3. For DXP 2024.Q2.x installations: Upgrade to version 2024.Q2.14 or later.
4. For DXP 2024.Q3.x installations: Upgrade to version 2024.Q3.14 or later.
5. For DXP 2024.Q4.x installations: Upgrade to version 2024.Q4.8 or later.
6. For Portal 7.4.x installations: Upgrade to version 7.4.3.133 or later.
7. After upgrade, verify the expandoTableLocalService authorization controls are properly enforced.
8. Review custom code or integrations that use expandoTableLocalService to ensure compatibility with the fixed version.

Caveat Review release notes for potential breaking changes between your current version and the target fixed version, particularly around expando/custom attributes functionality

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
Testing12.0 h
Review / QA4.0 h

28.0 hours of engineering $4,760

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

liferay.devVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-43773 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2025-43773?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to 2024.Q1.19 / 2025.Q1.15 or later

Severity 9.1 Critical

Exploit likelihood EPSS, next 30 days 0.3%

Affects: Digital Experience Platform

Remediation

A high-priority fix

Fix this in Digital Experience Platform 28 hrs · Moderate

Typical engagement from $4,760

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2025-43773 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References