dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-1870

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-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 Thim Kit for Elementor – Pre-built Templates & Widgets for Elementor plugin for WordPress is vulnerable to unauthorized access of data due to a missing validation checks on the 'thim-ekit/archive-course/get-courses' REST endpoint callback function in all versions up to, and including, 1.3.7. This makes it possible for unauthenticated attackers to disclose private or draft LearnPress course content by supplying post_status in the params_url payload.

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 · moderate confidence

This is an Insecure Direct Object Reference (IDOR) vulnerability in the Thim Kit for Elementor WordPress plugin. The REST endpoint 'thim-ekit/archive-course/get-courses' lacks proper authorization checks, allowing unauthenticated attackers to query private or draft LearnPress course content by manipulating the post_status parameter in the request.

MitigationUpdate the plugin to a patched version once available. Until then, consider restricting access to the WordPress REST API or implementing additional authentication for the affected endpoint.

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. Verify Thim Kit for Elementor is installed
    Navigate to WordPress admin > Plugins and confirm 'Thim Kit for Elementor' or 'Thim Elementor Kit' is installed and active, or check via WP-CLI: wp plugin list --name='*thim*' --status=active
    Affected if The plugin is installed and active on the site
  2. Check the installed plugin version
    In WordPress admin > Plugins > Thim Kit for Elementor, note the version number displayed, or run: wp plugin get thim-elementor-kit --field=version
    Affected if Any version of the plugin is installed; no patched version range is specified in the CVE advisory
  3. Confirm LearnPress LMS is installed
    In WordPress admin > Plugins, verify 'LearnPress' or 'LMS by ThimPress' is installed, or check via: wp plugin list --name='*learnpress*' --status=active
    Affected if LearnPress is installed as the vulnerability targets LearnPress course content
  4. Test the vulnerable REST endpoint access
    Send an unauthenticated GET request to: /wp-json/thim-ekit/v1/archive-course/get-courses (or /wp-json/thim-ekit/archive-course/get-courses) and verify a response is returned without authentication
    Affected if The endpoint returns a successful response without requiring authentication
  5. Verify private/draft course enumeration is possible
    Send a request to the endpoint with post_status parameter set to 'private' or 'draft' (e.g., ?post_status=private) and check if private or draft course data is returned in the response
    Affected if Private or draft LearnPress course content is exposed in the API response without authorization

A site is affected if it has the Thim Kit for Elementor plugin installed with the vulnerable REST endpoint accessible without authentication and LearnPress courses exist that could be enumerated.

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 the plugin to a patched version once available. Until then, consider restricting access to the WordPress REST API or implementing additional authentication for the affected endpoint.

Recommended fix High confidence

1.3.8 or later (latest version from WordPress repository)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Thim Kit for Elementor' plugin
  4. Check the current version installed
  5. If the installed version is 1.3.7 or lower, update the plugin to the latest available version

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

Have this fixed 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 help mitigating

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-2026-1870 — 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-2026-1870 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