Security Resilience

CVE-2024-1209

Info Disclosure in Learndash ≤ 4.10.3

Public PoCInfo Disclosure
Published
05 February 2024
Modified
17 June 2026
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS Score 0.024 84th percentile
Risk Priority 64 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-1209 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor (CWE-200) vulnerability in Learndash Learndash. Its CVSS base score is 5.3 (Medium).

Operationally, ranked in the top 16% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

The CVE-2024-1209 vulnerability is a sensitive information exposure issue in the LearnDash LMS plugin for WordPress, present in all versions through 4.10.1. It stems from insufficient protection of uploaded assignment files, which permits direct file access and is tracked under CWE-200 with a CVSS 3.1 score of 5.3.

Unauthenticated attackers can exploit the flaw remotely without credentials or user interaction to retrieve the contents of assignment uploads that should otherwise remain restricted.

References including LearnDash release notes and Wordfence threat intelligence entries point to patched versions that remediate the direct-access exposure. The associated EPSS values remain essentially flat near 0.47 with no material rise from a low baseline.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

The LearnDash LMS plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 4.10.1 via direct file access due to insufficient protection of uploaded assignments. This makes it possible for unauthenticated attackers to obtain…

more

those uploads.

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-1208Same product: Learndash Learndash
CVE-2024-1210Same product: Learndash Learndash
CVE-2024-56940Same product: Learndash Learndash
CVE-2024-56938Same product: Learndash Learndash
CVE-2023-3105Same product: Learndash Learndash
CVE-2024-56939Same product: Learndash Learndash
CVE-2023-28777Same product: Learndash Learndash
CVE-2022-20821Shared CWE-200
CVE-2025-25209Shared CWE-200
CVE-2025-55342Shared CWE-200

Affected Assets

learndash
learndash
≤ 4.10.3

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Access enforcement directly stops unauthorized actors from obtaining sensitive information.

Information flow enforcement structurally prevents sensitive data from reaching unauthorized recipients.

Protection of information at rest prevents unauthorized exposure of stored sensitive data.

Transmission confidentiality mechanisms stop exposure of sensitive data on the wire.

Least privilege reduces the set of actors who can reach sensitive information.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

A.5.10 only requires awareness, a topic-specific acceptable-use policy stating expected behaviours/monitoring, and procedures referencing classification and other controls; per the owner's explicit rule on labelling and similar dependency-style clauses, this does not itself prevent exposure (CWE-200) unless access/DLP/etc. act on it.

blocks

Requiring the return of all physical and electronic assets plus secure deletion of organizational data from personal devices reduces the chance that sensitive information remains accessible to departing personnel.

blocks

A.5.12 only defines and communicates a classification scheme so that protection needs can be understood; per the owner's explicit rule, labeling/classification does not itself prevent exposure and requires other controls (e.g. access enforcement) to act on it.

blocks

By requiring classification labels and metadata on all information assets, the control makes it harder for sensitive data to be inadvertently exposed because downstream systems and users can recognize and enforce handling rules based on those labels.

blocks

Requiring encryption, access controls, and recipient authentication for transfers directly reduces the chance that sensitive data reaches an unauthorized observer.

blocks

Secure delivery, protected storage, and confidentiality of allocation records limit exposure of authentication material to unauthorized observers.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

References