Security readout for executives and security teams
Plain-English summary
This vulnerability lets a logged-in remote user view Liferay DDMStructure data they should not be allowed to see. It is an authorization flaw, not an unauthenticated takeover. Business impact depends on what structure metadata is exposed and who can obtain authenticated access.
Executive priority
Prioritize remediation for externally accessible Liferay systems with broad user bases. The issue is not described as critical, but it can expose internal structure information to users who should not have it.
Technical view
Liferay Data Engine failed to enforce permissions in DataDefinitionResourceImpl.getSiteDataDefinitionByContentTypeByDataDefinitionKey. In affected Liferay Portal 7.3.0 through 7.3.5 and Liferay DXP 7.3 before fix pack 1, authenticated users could retrieve DDMStructures via GET API calls.
Likely exposure
Exposure is limited to organizations running the specified Liferay Portal or DXP 7.3 versions. Risk increases where many external, low-privilege, partner, or customer accounts can authenticate to the instance.
Exploitation context
The source bundle states remote authenticated access is required. It does not cite public exploitation, CISA KEV listing, exploit code, or unauthenticated access. Treat it as confirmed information disclosure with incomplete public severity data.
Researcher notes
Public data is sparse: no CVSS, CWE, or detailed vendor workaround is present in the provided bundle. The key test condition is whether permission checks block low-privilege access to DDMStructure retrieval through the named Data Engine method/API behavior.
Mitigation direction
- Apply Liferay DXP 7.3 fix pack 1 or later where applicable.
- For Liferay Portal 7.3.0-7.3.5, check Liferay guidance for the corrected release.
- Limit access for low-privilege authenticated users until remediation is complete.
- Review exposed Data Engine API access paths and authentication policies.
- Monitor for unusual Data Engine GET requests from non-administrative accounts.
Validation and detection
- Inventory Liferay Portal and DXP versions across internet-facing and internal deployments.
- Confirm DXP 7.3 systems are at fix pack 1 or later.
- Identify Portal 7.3.0-7.3.5 instances and map their exposure.
- Use authorized testing to verify low-privilege users cannot view DDMStructures.
- Review logs for unexpected DDMStructure retrieval by ordinary authenticated users.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CVE-2021-29052 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.