dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43798

MEDIUM · 6.5 CVSS v3.1 Published 2025-09-15
Fix available
A fix is available. Upgrade to 2023.q3.5 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
Liferay DXP 2023.Q4.0, 2023.Q3.1 through 2023.Q3.4, 7.4 GA through update 92 and 7.3 GA through update 35 allows a time-based one-time password (TOTP) to be used multiple times during the validity period, which allows attackers with access to a user’s TOTP to authenticate as the user.

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

Limerick DXP's TOTP authentication implementation fails to invalidate one-time passwords after single use, allowing a captured TOTP code to be replayed multiple times within its typical 30-second validity window to authenticate as the victim user.

MitigationApply vendor patches for the affected versions (2023.Q4.0, 2023.Q3.1-Q3.4, 7.4 through update 92, 7.3 through update 35) which enforce one-time use of TOTP codes server-side.

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

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 installed Lifer DXP version
    Navigate to Control Panel > Configuration > Server Administration > Product Information, or check the OSGi bundle version file in the Lifer home directory. Look for version strings like 2023.q3.x, 7.3.x, 7.4.x, or 2023.q4.0.
    Affected if The version matches any of: >= 2023.q3.1 and < 2023.q3.5; exactly 7.3.x; exactly 7.4.x; exactly 2023.q4.0
  2. Verify TOTP-based two-factor authentication is configured
    Check if any users or roles have TOTP/Time-based OTP enabled in Control Panel > Users and Organizations > User > Authentication > Two-Factor Authentication, or inspect the portal-ext.properties file for totp.enabled=true or similar TOTP configuration keys.
    Affected if TOTP authentication is enabled or configured for any user or system-wide setting in the affected version range
  3. Confirm the one-time-use behavior is not enforced
    Attempt to use the same TOTP code within its 30-second validity window twice: generate a valid TOTP code, use it once to authenticate, then immediately attempt to reuse the same code before the window expires. If the second attempt succeeds, the vulnerability is present.
    Affected if The same TOTP code successfully authenticates multiple times within its typical 30-second validity window

A defender is affected if their Lifer DXP version falls within the listed ranges AND TOTP two-factor authentication is enabled, and reusing the same TOTP code within its validity window grants multiple successful authentications.

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

Apply vendor patches for the affected versions (2023.Q4.0, 2023.Q3.1-Q3.4, 7.4 through update 92, 7.3 through update 35) which enforce one-time use of TOTP codes server-side.

Recommended fix Moderate confidence

2023.Q3.5 (for 2023.Q3.x branch); subsequent quarterly release for 2023.Q4.0; update 36+ for 7.3 GA; update 93+ for 7.4 GA

  1. 1. Back up your Limerick DXP database and configuration files before any upgrade.
  2. 2. Review the Lifera DXP Upgrade Guide for your specific version path at https://learn.lifera.com/
  3. 3. Upgrade from 2023.Q3.1-2023.Q3.4 to 2023.Q3.5 or later.
  4. 4. For Lifera DXP 7.3, apply the available security update (GA through update 35 is vulnerable; apply update 36 or later).
  5. 5. For Lifera DXP 7.4, apply the available security update (GA through update 92 is vulnerable; apply update 93 or later).
  6. 6. For Lifera DXP 2023.Q4.0, upgrade to the subsequent quarterly release (2024.Q1.0 or later).
  7. 7. After upgrade, verify TOTP functionality works correctly and test authentication flows.
  8. 8. Confirm the fix by verifying that reused TOTP codes are rejected during their validity period.
Caveat Review release notes for breaking changes between versions; some configuration changes may be required for quarterly upgrade paths

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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