LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47798: Account lockout in Liferay Portal 7.2.0 through 7.3.0, and older unsupported versions, and Liferay DXP 7.2...

Account lockout in Liferay Portal 7.2.0 through 7.3.0, and older unsupported versions, and Liferay DXP 7.2 before fix pack 5, and older unsupported versions does not invalidate existing user sessions, which allows remote authenticated users to remain authenticated after an account has been locked.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw means locking a Liferay user account may not kick out sessions that already exist. A user who is already signed in could remain active after the account is locked. Business impact depends on what those accounts can access, but the issue weakens account lockout as a containment control.

Executive priority

Schedule remediation in the normal vulnerability cycle, with faster handling for public or privileged Liferay deployments. This is medium severity, but it can undermine incident response because account lockout may not immediately stop access.

Technical view

CVE-2023-47798 is a CWE-384 session-management issue in Liferay Portal and DXP. Existing user sessions are not invalidated when an account is locked, allowing continued authenticated access after lockout. Sources list Portal 7.2.0 through 7.3.0 and older unsupported versions, plus DXP 7.2 before fix pack 5 and older unsupported versions.

Likely exposure

Exposure is most likely where affected Liferay Portal or DXP versions are internet-facing or used for sensitive business workflows. The issue requires an existing session, so risk is higher for privileged, partner, or customer accounts where lockout is expected to immediately contain access.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The weakness is not described as unauthenticated takeover; it is continued use of an already authenticated session after lockout. Treat lockout as incomplete containment until the affected system is fixed or verified.

Researcher notes

There is a notable wording tension: the CVSS vector has PR:N and UI:R, while the description says remote authenticated users remain authenticated after lockout. Use vendor guidance and local testing to confirm exact attack preconditions and fixed builds.

Mitigation direction

  • Review the Liferay advisory for fixed versions and supported remediation paths.
  • Apply Liferay DXP 7.2 fix pack 5 or later where applicable.
  • Upgrade or retire older unsupported Liferay Portal and DXP versions.
  • Prioritize remediation for systems handling privileged or sensitive user sessions.
  • Confirm any session invalidation workaround is vendor-supported before relying on it.

Validation and detection

  • Inventory Liferay Portal and DXP versions and fix pack levels.
  • Identify Portal 7.2.0 through 7.3.0 and older unsupported deployments.
  • Identify DXP 7.2 deployments before fix pack 5.
  • In non-production, verify locked accounts lose existing sessions after remediation.
  • Review logs for locked accounts that continued activity afterward.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-384: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-47798 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2023-47798Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LiferayPortal7.2.0unknown
LiferayDXP7.2.10unknown
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-384 · source CWE mapping

Session Fixation

Session Fixation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.