CVE-2025-43798 — com.liferay.multi.factor.…
Fix: liferay/liferay-portal@1df25e4CVE-2025-43798 is a CWE-304 vulnerability in com.liferay:com.liferay.multi.factor.authentication.timebased.otp.web. A fix is available for com.liferay:com.liferay.multi.factor.authentication.timebased.otp.web — see the affected versions and patch details below.
Liferay DXP Missing Critical Step in Authentication
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-43798.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
com.liferay:com.liferay.multi.factor.authentication.timebased.otp.webReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.liferay:com.liferay.multi.factor.authentication.timebased.otp.web | all versions | 2.0.25com.liferay:com.liferay.multi.factor.authentication.timebased.otp.web:2.0.25 |
Affected Products
digital experience platformliferayDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.liferay:com.liferay.multi.factor.authentication.timebased.otp.web, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.liferay:com.liferay.multi.factor.authentication.timebased.otp.web to 2.0.25 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-43798 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2025-43798 in your dependencies?
Find it across Maven, including transitive dependencies.