Custom Post Type Lockdown: Privilege escalation or authentication bypass
Custom Post Type Lockdown is affected by privilege escalation or authentication bypass. Exposure depends on how the affected operation is made reachable by the site. A successful request can grant permissions or access that the caller should not possess.
- Component
- Custom Post Type Lockdown
- Plugin slug
custom-post-type-lockdown- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Jan 16, 2025
This CVE was published Jan 16, 2025 and is one of 1 known issue for this plugin.
Update, patch or deactivate.
Update Custom Post Type Lockdown to a release outside the affected range, or disable and remove it until a fixed version is available.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
Cross-Site Request Forgery (CSRF) vulnerability in yonisink Custom Post Type Lockdown custom-post-type-lockdown allows Privilege Escalation.This issue affects Custom Post Type Lockdown: from n/a through <= 1.11.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H