CVE-2024-5648
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe LearnDash LMS – Reports plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on several functions (i.e. wrld_set_configuration, wrld_exclude_settings_save, apply_time_tracking_settings, wp_ajax_wrld_gutenberg_block_visit, etc..) in all versions up to, and including, 1.8.2.1. This makes it possible for authenticated attackers, with subscriber-level access and above, to update various plugin settings.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe LearnDash LMS – Reports plugin for WordPress has multiple AJAX endpoints (wrld_set_configuration, wrld_exclude_settings_save, apply_time_tracking_settings, wp_ajax_wrld_gutenberg_block_visit) that lack proper capability validation, allowing any authenticated user with subscriber-level privileges to modify plugin settings via these unauthenticated-function calls.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if LearnDash LMS - Reports plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'LearnDash LMS - Reports' or check the plugins directory for the wrld-reports folderAffected if The plugin is not installed on the WordPress site
-
Determine the installed version of the LearnDash Reports pluginIn WordPress admin, go to Plugins > Installed Plugins and locate the LearnDash LMS - Reports plugin to view its version number, or inspect the main plugin file header in wp-content/plugins/wrld-reports/Affected if Version is unknown or cannot be determined from the plugin files
-
Compare your version to the patched releaseThe patched version is 1.8.2.2. Compare your installed version number to this baselineAffected if Installed version is lower than 1.8.2.2 (for example, 1.8.2.1, 1.8.0, etc.)
-
Inspect AJAX endpoint accessibility for capability checksCheck the plugin PHP files for the AJAX handlers wrld_set_configuration, wrld_exclude_settings_save, apply_time_tracking_settings, and wp_ajax_wrld_gutenberg_block_visit. Search for current_user_can() or similar capability validation calls within these handler functionsAffected if The AJAX handlers do not contain current_user_can() or any capability validation before processing requests
A site is affected if the LearnDash LMS - Reports plugin is installed with a version lower than 1.8.2.2 and the AJAX handlers lack proper capability validation, allowing any subscriber-level user to modify settings.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the plugin to version 1.8.2.2 or later which implements proper capability checks (e.g., current_user_can()) on all affected AJAX handlers.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5648 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-5648 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data