Security readout for executives and security teams
Plain-English summary
This issue lets someone reuse a valid CAPTCHA answer in affected Liferay versions. That can weaken business controls that rely on CAPTCHA to slow account abuse, spam, or repeated submissions. It is not described as data theft or system takeover in the provided sources.
Executive priority
Treat this as a targeted abuse-control issue. Prioritize remediation if affected Liferay sites expose registration, login, contact, or transaction forms to the internet.
Technical view
Liferay Portal 7.3.4 and 7.3.5, and Liferay DXP 7.3 before fix pack 1, used a SimpleCaptcha implementation that did not invalidate a CAPTCHA answer after use. A remote attacker could reuse that answer to repeat CAPTCHA-protected actions.
Likely exposure
Exposure is most likely on internet-facing Liferay sites using CAPTCHA-protected forms or workflows on the affected versions named in the CVE description.
Exploitation context
The source bundle does not show CISA KEV listing, active exploitation, exploit publication, CVSS, or CWE data. Abuse would depend on which CAPTCHA-protected actions are exposed.
Researcher notes
Evidence is limited to the CVE description and Liferay reference. No CVSS, CWE, exploit status, or detailed patch notes are included in the provided bundle.
Mitigation direction
- Apply Liferay DXP 7.3 fix pack 1 or later where applicable.
- Check Liferay’s advisory for Portal 7.3.4 and 7.3.5 remediation guidance.
- Prioritize public forms, registration, login, and high-volume submission workflows.
- Monitor CAPTCHA-protected endpoints for repeated submissions using identical challenge results.
Validation and detection
- Inventory Liferay Portal and DXP versions in production and staging.
- Identify workflows using SimpleCaptcha or CAPTCHA-protected actions.
- Confirm CAPTCHA answers cannot be reused after a successful action.
- Review logs for repeated CAPTCHA-protected actions from the same source.
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-29047 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.