Vulnerability in LearnPress (WordPress plugin) (CVE-2026-8383)
Summary
Vulnerability in LearnPress (WordPress plugin) (CVE-2026-8383). Risk of unauthorized operations or information disclosure. Exploitable via edit.
Original description
The description as published by the source.
The LearnPress WordPress plugin before 4.3.7 does not gate the edit context on one of its REST endpoint behind the edit_users capability, allowing unauthenticated visitors to retrieve each returned user's roles, full capabilities map, extra capabilities, locale, and registration date via a crafted request
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-8383 has been found in LearnPress (WordPress plugin).
Attackers can target a specific entry point like edit over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "LearnPress (WordPress plugin) CVE-2026-8383" on the vendor's site.
CVE-2026-8383 (LearnPress (WordPress plugin)) — CWE-862 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: edit / edit_users
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-862) exists in LearnPress (WordPress plugin). Attackers reach the vulnerable code path via edit without authentication.
Check the vendor advisory for the affected versions of LearnPress (WordPress plugin). Attack surface: edit / edit_users.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで LearnPress (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web nvd.nist.gov
- web wpscan.com
- web github.com
- web contact@wpscan.com