CVE-2025-30549
📋 TL;DR
A Cross-Site Request Forgery (CSRF) vulnerability in the Yummly Rich Recipes WordPress plugin allows attackers to trick authenticated administrators into performing unintended actions. This affects WordPress sites using the Yummly Rich Recipes plugin from all versions up to 4.2. The vulnerability requires an authenticated admin to be tricked into clicking a malicious link.
💻 Affected Systems
- Yummly Rich Recipes WordPress Plugin
⚠️ Manual Verification Required
This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.
Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).
🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.
- Review the CVE details at NVD
- Check vendor security advisories for your specific version
- Test if the vulnerability is exploitable in your environment
- Consider updating to the latest version as a precaution
⚠️ Risk & Real-World Impact
Worst Case
An attacker could trick an admin into changing plugin settings, modifying recipes, or potentially performing other administrative actions that the plugin allows.
Likely Case
Attackers could modify recipe content, change plugin configurations, or disrupt recipe functionality on affected sites.
If Mitigated
With proper CSRF protections, the attack fails and no unauthorized actions occur.
🎯 Exploit Status
Exploitation requires social engineering to trick an authenticated admin into clicking a malicious link while logged in.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Version 4.3 or later
Restart Required: No
Instructions:
1. Log into WordPress admin panel. 2. Navigate to Plugins > Installed Plugins. 3. Find Yummly Rich Recipes. 4. Click 'Update Now' if available. 5. Alternatively, download version 4.3+ from WordPress repository and manually update.
🔧 Temporary Workarounds
Implement CSRF Protection
allAdd custom CSRF tokens to plugin forms if immediate patching isn't possible
Temporary Deactivation
linuxDeactivate the plugin until patched if not actively needed
wp plugin deactivate yummly-rich-recipes
🧯 If You Can't Patch
- Implement strict access controls and limit admin sessions
- Use browser extensions that block CSRF attempts
🔍 How to Verify
Check if Vulnerable:
Check WordPress admin panel > Plugins > Yummly Rich Recipes version. If version is 4.2 or lower, you are vulnerable.Check Version:
wp plugin get yummly-rich-recipes --field=versionVerify Fix Applied:
Verify plugin version is 4.3 or higher in WordPress admin plugins page.📡 Detection & Monitoring
Log Indicators:
- Unexpected plugin configuration changes
- Admin actions without corresponding user intent
Network Indicators:
- POST requests to plugin endpoints without proper referrer headers
SIEM Query:
source="wordpress" AND (plugin="yummly-rich-recipes" AND version<="4.2")