CVE-2026-39528
Missing Authorization in WP Delicious Plugin Allows Unauthorized Access
Publication date: 2026-04-08
Last updated on: 2026-04-10
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wp_delicious | delicious_recipes | to 1.9.5 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-39528 is a Broken Access Control vulnerability found in the WordPress WP Delicious plugin versions up to and including 1.9.5. It occurs due to missing authorization, authentication, or nonce token checks in certain plugin functions. This flaw allows unauthenticated users to perform actions that normally require higher privileges.
The vulnerability is classified under the OWASP Top 10 category A1: Broken Access Control and has a CVSS score of 5.3, indicating a low severity impact.
How can this vulnerability impact me? :
This vulnerability allows unauthenticated attackers to perform privileged actions without proper authorization, potentially compromising the security of your WordPress site.
Although it is considered low priority and unlikely to be exploited for highly impactful threats, it can be used in mass-exploit campaigns targeting many websites indiscriminately.
Users of the affected plugin version are strongly advised to update to version 1.9.6 or later to mitigate this risk.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability arises from missing authorization checks in the WP Delicious plugin up to version 1.9.5, allowing unauthenticated users to perform privileged actions. Detection typically involves checking the plugin version and monitoring for unauthorized access attempts to plugin-specific endpoints or functions.
To detect if your system is vulnerable, first verify the installed version of the WP Delicious plugin. For WordPress, you can use the following command to check the plugin version via WP-CLI:
- wp plugin list --status=active
Look for "delicious-recipes" and check if the version is less than or equal to 1.9.5.
Additionally, monitoring web server logs for suspicious unauthenticated requests targeting WP Delicious plugin endpoints or unusual POST requests without valid authentication tokens may help identify exploitation attempts.
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation step is to update the WP Delicious plugin to version 1.9.6 or later, where this vulnerability has been fixed.
If immediate updating is not possible, consider temporarily disabling the plugin to prevent exploitation.
Additionally, implement web application firewall (WAF) rules to block unauthenticated requests attempting to access privileged plugin functions.
Using automated patch management tools or services like Patchstack that offer auto-updates for vulnerable plugins can also help mitigate the risk.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
CVE-2026-39528 is a Broken Access Control vulnerability that allows unauthenticated users to perform actions requiring higher privileges due to missing authorization checks in the WP Delicious plugin. Such unauthorized access can lead to potential data exposure or manipulation.
While the vulnerability has a low severity score (CVSS 5.3) and is considered unlikely to be exploited for impactful threats, any unauthorized access or data breach could potentially affect compliance with standards like GDPR or HIPAA, which require strict access controls and protection of sensitive data.
Therefore, organizations using the affected plugin versions should promptly update to the patched version (1.9.6 or later) to maintain compliance with these regulations by ensuring proper access control mechanisms are in place.