CVE-2025-13964
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 LearnPress – WordPress LMS Plugin plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the catch_lp_ajax function in all versions up to, and including, 4.3.2. This makes it possible for unauthenticated attackers to modify course contents by adding/removing/updating/re-ordering sections or modifying section items.
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 LearnPress WordPress LMS plugin fails to enforce authorization checks on its catch_lp_ajax function, allowing unauthenticated users to make AJAX calls that modify course data. Attackers can add, remove, update, or reorder course sections and items without any authentication or capability verification.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify LearnPress plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and confirm LearnPress is listed and activeAffected if LearnPress plugin is present and active in WordPress
-
Determine installed LearnPress versionCheck the plugin file header in wp-content/plugins/learnpress/learnpress.php or view the plugin version displayed in the Plugins admin pageAffected if Version is lower than 4.3.2 (vulnerable versions are any release before 4.3.2)
-
Inspect the catch_lp_ajax function for authorization gapsAccess the plugin source file containing catch_lp_ajax function and verify if current_user_can() or similar capability checks are performed before processing AJAX requestsAffected if No capability verification (current_user_can) is found in the catch_lp_ajax function or its called methods
-
Test AJAX endpoint accessibility without authenticationSend a crafted POST request to your site's wp-admin/admin-ajax.php with a LearnPress AJAX action (such as lp_update_course_section order) without including any authentication cookies or noncesAffected if The AJAX call executes successfully and modifies course data without returning an authentication or capability error
You are affected if LearnPress is installed with a version earlier than 4.3.2 and the catch_lp_ajax function processes requests without verifying user authentication or capabilities.
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.
dbcve · scopedUpdate LearnPress to version 4.3.2 or later, and implement proper capability checks (current_user_can()) and nonce validation on all AJAX endpoints in the catch_lp_ajax function.
Latest version of LearnPress (beyond 4.3.2)
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'LearnPress – WordPress LMS Plugin'
- Click 'Update Now' if an update is available, or manually download the latest version from wordpress.org/plugins/learnpress and upload it
- Verify the update to a version higher than 4.3.2 was successful
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13964 — 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-2025-13964 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