CVE-2026-4365
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 plugin for WordPress is vulnerable to unauthorized data deletion due to a missing capability check on the `delete_question_answer()` function in all versions up to, and including, 4.3.2.8. The plugin exposes a `wp_rest` nonce in public frontend HTML (`lpData`) to unauthenticated visitors, and uses that nonce as the only security gate for the `lp-load-ajax` AJAX dispatcher. The `delete_question_answer` action has no capability or ownership check. This makes it possible for unauthenticated attackers to delete any quiz answer option by sending a crafted POST request with a publicly available nonce.
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 plugin exposes a wp_rest nonce in public HTML (lpData) visible to unauthenticated visitors, and uses this nonce as the sole authentication mechanism for the lp-load-ajax dispatcher. The delete_question_answer() function lacks any capability or ownership verification, allowing any unauthenticated attacker with the publicly-revealed nonce to delete arbitrary quiz answers via crafted POST requests.
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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
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.
-
Confirm LearnPress plugin is installedInspect WordPress plugins directory or check wp-content/plugins folder for learnpress folder, or view installed plugins via WordPress adminAffected if LearnPress plugin is present in the WordPress installation
-
Check for exposed nonce in public page sourceView source HTML of any public-facing LearnPress page (e.g., a course or quiz page) and search for 'lpData' or 'wp_rest' nonce string visible in script tags accessible to unauthenticated usersAffected if A wp_rest nonce value is visible in public HTML source to unauthenticated visitors
-
Verify lp-load-ajax endpoint accepts unauthenticated requestsSend a crafted POST request to /wp-admin/admin-ajax.php?action=lp-load-ajax (or the site's AJAX endpoint) without authenticating and observe if the endpoint responds rather than returning an authentication errorAffected if The AJAX dispatcher accepts requests without requiring user authentication
-
Test delete_question_answer action accessibilitySend a POST request to the lp-load-ajax endpoint with action=delete_question_answer and a target question/answer ID, using only the publicly-exposed nonce, without any authenticated sessionAffected if The request executes without returning a capability or authentication error, indicating the function lacks ownership verification
If LearnPress is installed and the wp_rest nonce is exposed in public HTML, the environment is affected and allows unauthenticated quiz answer deletion via the delete_question_answer function.
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.
From vendor dataRestrict the delete_question_answer AJAX action to authenticated users with proper capability checks (e.g., manage_options), validate ownership of the quiz/question before deletion, and never expose wp_rest nonces to unauthenticated users - use nonces intended for public use or implement proper authentication.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4365 — 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-2026-4365 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