dbcve.org
LearnpressWordPress extension · Thimpress

CVE-2024-3560

MEDIUM · 5.4 CVSS v3.1 Published 2024-04-19
Fix available
A fix is available. Upgrade to 4.2.6.5 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 Stored Cross-Site Scripting via the _id value in all versions up to, and including, 4.2.6.4 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 versions up to 4.2.6.4 contain a stored XSS vulnerability in the _id parameter. Authenticated attackers with contributor-level access can inject malicious JavaScript through insufficiently sanitized input, which persists in the database and executes when users access affected pages.

MitigationUpdate to the latest LearnPress version and implement proper input sanitization and output escaping on the _id parameter and similar user-supplied attributes throughout the plugin.

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.5

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. Check LearnPress plugin version
    Go to WordPress admin > Plugins > Installed Plugins > LearnPress. Compare the installed version to 4.2.6.5. Versions below 4.2.6.5 are affected.
    Affected if Installed version is 4.2.6.4 or lower
  2. Identify contributor-level user accounts
    Navigate to WordPress admin > Users. Review the user list for accounts with the Contributor role, as this access level can exploit the vulnerability.
    Affected if Any contributor-level accounts exist in the system
  3. Inspect database for malicious _id values
    Query your WordPress database (e.g., via phpMyAdmin) for suspicious scripts in tables that store LearnPress data, specifically looking for XSS payloads in any field that might correspond to an _id parameter. Search for patterns like <script, javascript:, onload, onerror in postmeta or LearnPress custom tables.
    Affected if Database contains entries with malicious script tags or event handlers in LearnPress-related fields
  4. Review recent LearnPress course/lesson content
    Check the wp_posts table for recently added or modified LearnPress items (courses, lessons, quizzes) authored by contributor-level users. Inspect the post_content and any custom meta fields for injected scripts.
    Affected if Recent content authored by contributors contains unsanitized script tags or HTML attributes
  5. Check if LearnPress is actively used
    Verify whether LearnPress courses, lessons, or quiz features are currently published and accessible on the site. The vulnerability only affects environments where the plugin functionality is in use.
    Affected if LearnPress is active with published courses or lessons that could be accessed by users

You are affected if LearnPress version is below 4.2.6.5 AND the plugin is active AND contributor-level users exist or suspicious script patterns are found in the database.

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.5 or later
Fixed in 4.2.6.5
Interim mitigation

Update to the latest LearnPress version and implement proper input sanitization and output escaping on the _id parameter and similar user-supplied attributes throughout the plugin.

Recommended fix High confidence

4.2.6.5

  1. Backup your WordPress database and files before making any changes
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Find LearnPress (or LearnPress – WordPress LMS Plugin) in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 4.2.6.5
  5. After updating, verify the plugin version shows 4.2.6.5 or higher

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

Fix this in Learnpress Scoped from the published advisory
  • Consultation3.0 h
  • Implementation5.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,310
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-3560 — 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-3560 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