dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-39528

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-08
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
Missing Authorization vulnerability in WP Delicious WP Delicious delicious-recipes allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Delicious: from n/a through <= 1.9.5.

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

Missing authorization vulnerability in WP Delicious delicious-recipes WordPress plugin allows exploitation of incorrectly configured access control security levels, potentially enabling unauthenticated users to access sensitive functionality that should require proper authentication and authorization checks.

MitigationApply vendor patch when available; until then, restrict plugin admin access to trusted users only and monitor for unauthorized administrative actions.

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. Confirm the delicious-recipes plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Delicious Recipes' or 'WP Delicious' in the installed plugins list, or check the /wp-content/plugins/delicious-recipes/ directory exists on the server
    Affected if The plugin is installed and active on the WordPress site
  2. Identify the installed plugin version
    In WordPress admin > Plugins > Delicious Recipes, view the plugin details to see the version number, or open the main plugin file (such as delicious-recipes.php) and look for the 'Version:' header in the plugin comment block
    Affected if The displayed version is lower than 1.9.6 (versions 1.9.5 and below are indicated as vulnerable)
  3. Verify the site exposes vulnerable endpoints
    Check if the plugin AJAX endpoints are accessible without authentication by examining the plugin's ajax-handlers.php or similar files for wp_ajax_ and wp_ajax_nopriv_ hooks, or test accessing known admin functions while logged out
    Affected if AJAX or admin actions registered with wp_ajax_nopriv_ hooks or missing capability checks (like current_user_check or permission callbacks) are found in the plugin code
  4. Review user role configuration
    In WordPress admin > Delicious Recipes > Recipe Settings > User Roles, examine which user roles have access to recipe management features and verify if lower-privileged roles (like Editor or Author) can access administrative functions
    Affected if Users with Subscriber, Contributor, or Author roles can access features intended for Administrator role only
  5. Check for unauthorized recipe management access
    Attempt to access recipe creation, editing, or deletion functions with a low-privileged user account, or review the server access logs for requests to /wp-admin/admin-ajax.php?action=dr_* from unauthenticated or low-privilege users
    Affected if Lower-privileged or unauthenticated users can successfully create, modify, or delete recipes that should require administrator capabilities

The site is affected if the delicious-recipes plugin is installed with a version lower than 1.9.6 and unauthenticated or low-privileged users can access administrative functionality without proper authorization checks.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch when available; until then, restrict plugin admin access to trusted users only and monitor for unauthorized administrative actions.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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