dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-13956

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 unauthorized access of data due to a missing capability check on the statistic function in all versions up to, and including, 4.3.1. This makes it possible for unauthenticated attackers to view the plugin's orders statistics, including total revenue summaries and order status counts

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.3.1 contain a broken access control vulnerability where the statistic function lacks a capability check (e.g., current_user_can()). This allows any unauthenticated visitor to access the plugin's order statistics endpoint and view sensitive financial data including total revenue summaries and order status counts.

MitigationUpdate to version 4.3.2 or later which includes proper capability checks. If an update is unavailable, use web application firewall rules or server-level access controls to restrict access to the affected statistic function to authenticated administrators only.

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 installed LearnPress version
    Navigate to WordPress admin > Plugins > Installed Plugins > LearnPress, or inspect the main plugin file (learnpress.php) for the 'Version' header comment
    Affected if Version is 4.3.1 or lower (any version up to 4.3.1)
  2. Identify the statistics endpoint
    Check the LearnPress plugin files for the order statistics function. Common paths include /inc/admin/class-*-statistics.php or similar admin class files. Look for functions handling order/revenue data.
    Affected if The plugin file contains a statistics or order-summary function without a current_user_can() capability check
  3. Test unauthenticated access to statistics endpoint
    Using a tool like curl or a browser private/incognito window, attempt to access known LearnPress admin-ajax endpoints or REST API routes related to statistics (e.g., /wp-admin/admin-ajax.php?action=lp_orders_stats or similar). Do not log in before making the request.
    Affected if The endpoint returns financial data (revenue totals, order counts, order status breakdown) without requiring login authentication

A user is affected if their LearnPress version is 4.3.1 or lower AND the statistics endpoint responds with financial data to unauthenticated requests.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 4.3.2 or later which includes proper capability checks. If an update is unavailable, use web application firewall rules or server-level access controls to restrict access to the affected statistic function to authenticated administrators only.

Recommended fix Moderate confidence

LearnPress plugin version 4.3.2 or latest stable release

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find LearnPress – WordPress LMS Plugin
  4. If an update is available, click 'Update Now' to update to the latest version (4.3.2 or higher)
  5. Alternatively, upload the latest LearnPress plugin zip file from wordpress.org/plugins/learnpress/
  6. After updating, verify the plugin version shows 4.3.2 or higher under Plugins > Installed Plugins
  7. Test that the statistic functionality now requires proper authentication by confirming unauthenticated requests no longer expose order data

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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