dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43814

MEDIUM · 6.5 CVSS v3.1 Published 2025-09-22
Fix available
A fix is available. Upgrade to 7.4.3.113 / 2023.Q4.9 or later.
See remediation →
71/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
In Liferay Portal 7.4.0 through 7.4.3.112, and older unsupported versions, and Liferay DXP 2023.Q4.0 through 2023.Q4.8, 2023.Q3.1 through 2023.Q3.10, 7.4 GA through update 92, and older unsupported versions the audit events records a user’s password reminder answer, which allows remote authenticated users to obtain a user’s password reminder answer via the audit events.

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

The audit logging system in Lifer Portal and DXP improperly records password reminder answers in audit event logs. This sensitive authentication recovery data is accessible to any authenticated user who can view audit events, enabling unauthorized disclosure of password reminder answers.

MitigationConfigure audit logging to exclude password reminder answer fields from being recorded, or apply vendor patches that prevent this sensitive data from being logged.

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.10>= 2023.Q4.0, < 2023.Q4.9= 7.4
Liferay PortalApplication
Affected:>= 7.2.0, < 7.4.3.113

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

CVSS:3.1/AV:N/AC:L/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. Identify Lifer Portal or DXP version
    Locate the installed Lifer version via the control panel (Server > Information) or check the portal-ext.properties file for the version property. Compare against the affected ranges: DXP 2023.Q3.1 to 2023.Q3.10, 2023.Q4.0 to 2023.Q4.9, and 7.4; Portal 7.2.0 to 7.4.3.112
    Affected if The installed version falls within any of the listed affected version ranges
  2. Confirm audit logging is enabled
    Verify the audit logging module is active by checking the Lifer control panel under Configuration > Audit, or inspect the portal-ext.properties for audit.framework.enabled=true
    Affected if Audit logging is enabled and the version is vulnerable
  3. Examine audit event logs for password reminder data
    Access the audit log viewer (typically at /audit//view or via the Events section in the control panel) and search for events containing fields related to password reminder answers, such as 'reminderQueryAnswer' or similar authentication recovery data
    Affected if Audit logs contain password reminder answer fields in any recorded events
  4. Verify user access to audit events
    Check the roles and permissions assigned to users to determine which authenticated users can view audit events. Typically found under Roles > Permissions for the Audit portlet
    Affected if Any authenticated users (beyond administrators) have permission to view audit event logs

If the Lifer version is within the affected ranges, audit logging is enabled, and users with audit view access exist, then password reminder answers may be exposed in the audit logs.

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.113 / 2023.Q4.9 or later
Fixed in 7.4.3.1132023.Q4.9
Interim mitigation

Configure audit logging to exclude password reminder answer fields from being recorded, or apply vendor patches that prevent this sensitive data from being logged.

Recommended fix High confidence

LPortal: 7.4.3.113+ | LXP: 2023.Q4.9+

  1. Identify the exact Liferay Portal or DXP version currently running using the Control Panel or server logs
  2. For LPortal 7.4.x: Upgrade to version 7.4.3.113 or later
  3. For LXP 2023.Q4.x: Upgrade to version 2023.Q4.9 or later
  4. For LXP 2023.Q3.x: Upgrade to a version beyond 2023.Q3.10 (such as 2023.Q4.9 or later)
  5. After upgrade, verify that audit events no longer contain password reminder answers by reviewing recent audit logs
  6. Ensure the upgrade is tested in a non-production environment first
Caveat Review Lifera compatibility matrix for your specific version upgrade; major version jumps may require compatibility testing

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

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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