Security readout for executives and security teams
Plain-English summary
CVE-2021-24562 is an authorization flaw in the LifterLMS WordPress plugin before 4.21.2. A student could view another student’s answers and grades. This is primarily a privacy and trust issue for training, education, and membership sites rather than a system takeover based on the supplied sources.
Executive priority
Treat this as a moderate-priority privacy exposure. It can undermine learner confidentiality and may create regulatory or contractual concerns, but the provided sources do not indicate remote code execution or confirmed active exploitation.
Technical view
The issue is described as an IDOR mapped to CWE-639. LifterLMS before 4.21.2 did not properly restrict access to student-specific grade and answer data, allowing one authenticated student to access another student’s records. The provided sources do not include CVSS details, affected endpoints, or proof-of-concept mechanics.
Likely exposure
Exposure is likely limited to WordPress sites running LifterLMS before 4.21.2, especially sites with enrolled students, quizzes, answers, or grade records.
Exploitation context
The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. The described attacker context is a student accessing other students’ data through broken object-level authorization.
Researcher notes
Evidence is concise and incomplete. The bundle supports an authenticated student data-access issue in LifterLMS before 4.21.2, but does not provide CVSS, endpoint details, exploit prevalence, or broader product impact. Do not infer unauthenticated access from these sources.
Mitigation direction
- Upgrade LifterLMS to version 4.21.2 or later.
- Check vendor release notes for any additional security guidance.
- Limit student account creation where enrollment is not required.
- Review privacy incident handling if grades or answers may have been exposed.
Validation and detection
- Inventory WordPress sites for LifterLMS installations and versions.
- Confirm no production site is running LifterLMS before 4.21.2.
- Verify student role access cannot view other students’ grades or answers.
- Review logs for unusual access to grade or answer records.
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.
CWE-639: 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 lookupCVE-2021-24562 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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://wpscan.com/vulnerability/d45bb744-4a0d-4af0-aa16-71f7e3ea6e00CVE reference · x_refsource_MISC
- https://make.lifterlms.com/2021/05/17/lifterlms-version-4-21-2/CVE reference · x_refsource_MISC
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.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.