CVE-2025-67548
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 · uneditedMissing 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.1.
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 confidenceThe WP Delicious WordPress plugin versions up to 1.9.1 contain a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. This likely permits unauthorized users to perform actions that should require higher privileges.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Locate the WP Delicious plugin versionAccess your WordPress admin dashboard, go to Plugins > Installed Plugins, find 'WP Delicious' (or 'Delicious Recipes'), and read the version number displayed under the plugin name. Alternatively, inspect the main plugin file (e.g., wp-content/plugins/delicious-recipes/delicious-recipes.php) and look for the 'Version' header comment.Affected if The version displayed is 1.9.1 or lower (any version up to and including 1.9.1)
-
Confirm the plugin is activeIn the same Plugins screen in WordPress admin, verify that WP Delicious shows as 'Active' rather than 'Inactive' or 'Must Use'.Affected if The plugin is active and the version is 1.9.1 or lower
-
Check for exposed AJAX actions (optional)Inspect the plugin's PHP files in wp-content/plugins/delicious-recipes/ for AJAX action hooks (wp_ajax_ and wp_ajax_nopriv_ prefixes). Look for sensitive actions (such as settings saves, user data modifications, or content deletions) that may lack capability checks using current_user_can() or nonce validation.Affected if Sensitive AJAX endpoints are registered with wp_ajax_nopriv_ or lack proper capability checks and nonce verification
-
Review admin function access controlsExamine admin menu pages and callback functions in the plugin for proper authorization checks. Check if functions handling sensitive operations (plugin settings, recipe management, import/export) verify user capabilities before execution.Affected if Admin functions handling sensitive operations do not verify user capabilities or validate nonces
You are affected if the WP Delicious plugin is active and the installed version is 1.9.1 or lower, as this version range contains the missing authorization vulnerability.
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 dataUpdate the plugin to the latest version once available, or implement proper capability checks and nonce validation on all sensitive AJAX actions and admin functions within the plugin.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67548 — 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-2025-67548 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