🚨 **What is this?**
- **Essence**: A **privilege escalation** flaw in the **ACPT Custom Post Types** plugin.
- **Consequence**: Unauthenticated attackers can **bypass access controls** and gain admin-level power.
Q2根本原因？（CWE/缺陷点）
🔍 **Root Cause**
- **Flaw**: Improper **permission validation** & **access control**.
- **CWE**: Likely **CWE-862** (Missing Authorization).
- **Mechanism**: The plugin fails to properly check user roles before granting …
📦 **Who is Affected?**
- **Component**: **ACPT Custom Post Types** plugin for WordPress.
- **Versions**: **≤ 2.0.63**.
- **Scope**: Any WordPress site using this plugin in affected versions.
Q4黑客能干啥？（权限/数据）
💥 **What Can Hackers Do?**
- **Privileges**: **Unauthenticated** users can escalate to **Administrator**.
- **Data**: Full control over site settings, content, and user accounts.
- **Impact**: **CVSS 9.8 (Critical)** — H…
📉 **Exploitation Threshold**
- **Auth**: **None** (PR:N) — No login required!
- **Complexity**: **Low** (AC:L) — Easy to exploit.
- **User Interaction**: **None** (UI:N) — No clicks needed.
Q6有现成Exp吗？（PoC/在野利用）
🧪 **Public Exploits?**
- **PoC**: **None** listed in the data.
- **Wild Exploitation**: No confirmed in-the-wild attacks yet.
- **Status**: **Theoretical** risk until a PoC appears.
Q7怎么自查？（特征/扫描）
🔎 **How to Self-Check?**
- **Step 1**: Check plugin version in **WordPress Dashboard → Plugins**.
- **Step 2**: If version ≤ **2.0.63**, you are **at risk**.
- **Step 3**: Scan with **WPScan** or **Patchstack** for confi…
🛡️ **Is It Fixed?**
- **Official Fix**: Update to a version **> 2.0.63**.
- **Mitigation**: If no update available, **disable** the plugin or restrict access via **Web Application Firewall (WAF)**.
Q9没补丁咋办？（临时规避）
🔧 **No Patch? Workaround**
- **Option 1**: **Deactivate** the plugin if not critical.
- **Option 2**: Use **WAF rules** to block unauthenticated access to admin endpoints.
- **Option 3**: Manually audit **user roles** an…