dbcve.org
LearnpressWordPress extension · Thimpress

CVE-2024-4971

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-22
Fix available
A fix is available. Upgrade to 4.2.6.7 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
The LearnPress – WordPress LMS Plugin plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the ‘id’ parameter in all versions up to, and including, 4.2.6.6 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

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 confidence

The LearnPress WordPress LMS plugin fails to properly sanitize and escape the 'id' parameter, allowing unauthenticated attackers to inject malicious JavaScript via crafted URLs. This reflected XSS requires tricking users into clicking a malicious link to execute the payload.

MitigationUpdate LearnPress to version 4.2.6.7 or later to receive the patch. Until then, warn users against clicking untrusted links pointing to LearnPress pages.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LearnpressWordPress extension
Affected:< 4.2.6.7

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm LearnPress plugin is installed
    Check for the LearnPress plugin directory in wp-content/plugins/learnpress/ or look for 'LearnPress' in the WordPress plugins list at /wp-admin/plugins.php
    Affected if LearnPress plugin files are found on the server
  2. Identify installed LearnPress version
    Open wp-content/plugins/learnpress/learnpress.php and look for the 'Version:' header in the plugin comments, or check the version in the WordPress admin plugins list
    Affected if The displayed version number is lower than 4.2.6.7 (for example, 4.2.6.6, 4.2.5.x, etc.)
  3. Verify the vulnerable endpoint is reachable
    Attempt to access a LearnPress page with a test parameter such as ?id=test123 (for example, /courses/?id=test123) and verify the plugin processes the parameter
    Affected if The page loads and the id parameter value appears reflected in the HTML response without proper encoding
  4. Check for recent plugin updates
    In WordPress admin, go to Dashboard > Updates or the Plugins page to see if a newer version is available
    Affected if Version 4.2.6.7 or later is not available as an update

You are affected if LearnPress is installed and the version is below 4.2.6.7, making the reflected XSS via the id parameter potentially exploitable.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 4.2.6.7 or later
Fixed in 4.2.6.7
Interim mitigation

Update LearnPress to version 4.2.6.7 or later to receive the patch. Until then, warn users against clicking untrusted links pointing to LearnPress pages.

Recommended fix High confidence

LearnPress version 4.2.6.7

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find LearnPress in the plugin list
  4. Click 'Update now' if an update is available, or manually update to version 4.2.6.7
  5. Verify the update completed successfully
  6. Consider clearing site cache if using caching plugins

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Learnpress Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-4971 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-4971 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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