MEDIUM 5.3

CVE-2026-8383: LearnPress Plugin User Data Disclosure via REST API Authorization Bypass

A flaw in the LearnPress WordPress plugin before version 4.3.7 exposes sensitive user information to anyone on the internet without needing to log in. The plugin's REST API endpoint fails to properly restrict access to user details—specifically roles, capabilities, locale, and registration dates—which should only be available to administrators. An attacker can craft a simple web request to retrieve this data for any user on an affected site.

Source data · NVD / CISA · public domain

CVSS
3.1 · 5.3 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Weaknesses (CWE)
CWE-862
Affected products
0 configuration(s)
Published / Modified
2026-06-17 / 2026-06-17

NVD description (verbatim)

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

1 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-8383 is an authorization bypass vulnerability in LearnPress (versions prior to 4.3.7) affecting the WordPress REST API. The vulnerability stems from insufficient access control on an `edit` context REST endpoint that lacks the required `edit_users` capability check. This permits unauthenticated requests to enumerate and extract user role assignments, full capability maps, additional custom capabilities, locale settings, and account registration timestamps. The attack requires only network access and a crafted HTTP request; no authentication or user interaction is necessary. This is classified as missing or improper authorization (CWE-862).

Business impact

Exposure of user roles and capabilities enables reconnaissance for privilege escalation attempts and targeted attacks against high-privilege accounts. Registration dates and locale information, while seemingly minor, can inform social engineering campaigns and geographic targeting. For organizations using LearnPress in a learning management context, the leakage of administrative and instructor capability maps gives attackers a detailed roadmap of the site's permission structure, increasing the likelihood of successful account compromise or lateral movement. The scope is limited to information disclosure with no direct impact on integrity or availability.

Affected systems

LearnPress WordPress plugin versions before 4.3.7 are vulnerable. The vendor information is not available in the current threat intelligence; verify the exact affected version range directly against the official LearnPress plugin repository or vendor advisory. Any WordPress installation running an affected version with the plugin active and the REST API enabled is at risk.

Exploitability

This vulnerability is trivial to exploit. The attack vector is network-based, requires no authentication, and demands no complex conditions—the CVSS score of 5.3 (Medium) reflects this accessibility. An unauthenticated attacker can query the vulnerable endpoint from anywhere and receive user information in the response. No zero-day exploit code is required; standard REST API tooling suffices. However, the vulnerability is not currently listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, suggesting either recent disclosure or limited public weaponization at this time.

Remediation

Update LearnPress to version 4.3.7 or later immediately. The patch introduces proper capability gating on the affected REST endpoint, ensuring that the `edit_users` capability is enforced before sensitive user data is returned. Verify the update applies the necessary authorization checks. Until patching is possible, consider disabling or restricting REST API access via authentication plugins or web application firewall rules if operationally feasible.

Patch guidance

Patching is straightforward: upgrade LearnPress to version 4.3.7 or newer through the WordPress plugin management interface or command line. Test the update in a staging environment first to confirm compatibility with your site's configuration and other plugins. After deployment, verify that the REST endpoint no longer returns user roles and capabilities to unauthenticated requests. No configuration changes should be necessary post-patch.

Detection guidance

Monitor web server logs and WAF logs for REST API requests to LearnPress user endpoints (typically `/wp-json/...`) originating from unauthenticated sources. Look for repeated requests querying user data or patterns consistent with user enumeration. If your site uses WordPress audit logging plugins, check for access attempts to sensitive REST resources. Query your database or use WordPress admin tools to confirm you are running LearnPress 4.3.6 or earlier if you suspect potential exposure. Consider scanning for signs of unauthorized user enumeration or reconnaissance in your access logs dating back to when the vulnerable plugin version was active.

Why prioritize this

Although the CVSS score is Medium (5.3), this vulnerability should be prioritized for rapid patching because it enables information gathering for follow-on attacks. User capability exposure is a high-value reconnaissance tool for attackers planning privilege escalation or account takeover campaigns. The ease of exploitation—unauthenticated, network-accessible, low complexity—means the attack surface is large. Any WordPress site running LearnPress should treat this as a near-term remediation target, particularly if the site hosts administrative or instructor accounts or sensitive course data. The lack of KEV listing does not diminish the strategic risk.

Risk score, explained

The CVSS 5.3 Medium severity score reflects confidentiality impact (low, information disclosure only) with no integrity or availability impact. The attack vector is network, privilege requirement is none, and user interaction is not required—all factors increasing the score. The scope is unchanged (attacks do not jump privilege boundaries), limiting the severity. However, the score does not fully capture the reconnaissance value to threat actors; practitioners should weight this as a higher-priority patch than the numeric score alone suggests given the nature of the exposed data and typical attack workflows.

Frequently asked questions

Could an attacker use this to take over admin accounts?

Not directly. This vulnerability only discloses user roles and capabilities; it does not provide passwords or session tokens. However, knowing which accounts have elevated privileges enables attackers to focus brute-force, phishing, or exploitation efforts on high-value targets, making account compromise more likely downstream.

Does this affect sites with the REST API disabled?

No. If WordPress REST API is completely disabled via configuration or plugins, this endpoint would not be accessible. However, most modern WordPress installations leave REST API enabled by default for legitimate functionality, so most LearnPress users are likely affected.

Is updating to 4.3.7 safe?

Updates to close security vulnerabilities are strongly recommended and should be safe in a properly maintained WordPress environment. Always test updates on a staging site first to verify compatibility, but delaying a patch for this issue increases your exposure window significantly.

What if I cannot update immediately?

As a temporary mitigation, restrict REST API access at the web server or WAF level to authenticated users only, or disable the REST API entirely if your site does not depend on it. This will prevent unauthenticated requests from reaching the vulnerable endpoint. Implement monitoring for suspicious user enumeration attempts. Plan an update as soon as operationally possible.

This analysis is provided for informational purposes and based on the vulnerability disclosure dated 2026-06-17. Verify all patch version numbers, supported versions, and affected product lists directly against the official LearnPress vendor advisory or plugin repository before taking action. The absence of a CVE from CISA's Known Exploited Vulnerabilities list does not guarantee the vulnerability is not being actively exploited; it reflects known public exploitation at the time of curation. Organizations should assess their own risk based on exposure, business context, and threat landscape. No exploit code or weaponized proof-of-concept is provided here. Source: NVD (public-domain), retrieved 2026-07-27. Analysis generated by SEC.co (claude-haiku-4-5).