Custom Post Type Lockdown
Approved changes feed: RSS · Atom
cpe:2.3:a:yonisink:custom_post_type_lockdown:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Yonisink (875ce532-e05a-563a-b0aa-e370737effa7) |
|---|---|
| Product | Custom Post Type Lockdown (7b4bff33-b723-55ec-acec-9f1771dedafd) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-23530 |
vulnerable | 2026-06-08 07:10:55.917408 |
WordPress Custom Post Type Lockdown plugin <= 1.11 - CSRF to Privilege Escalation vulnerability
HIGH (8.8)
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.
Published: 2025-01-16T20:06:11.401Z
Updated: 2026-04-28T16:11:12.087Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.