Q: What can hackers do? (Privileges/Data)

🕵️ **Attacker Actions**: Modify arbitrary options (e.g., `users_can_register`, `default_role`). 👑 **Result**: Create new **Admin Accounts** and gain full control.

Q: Is exploitation threshold high? (Auth/Config)

🔓 **Threshold**: **LOW**. 🚫 **Auth Required**: **None**. Unauthenticated attackers can exploit this directly.

Q: Is there a public Exp? (PoC/Wild Exploitation)

💣 **Exploit**: **YES**. 🔗 Public PoC available on GitHub (RandomRobbieBF) and Nuclei templates.

Q: How to self-check? (Features/Scanning)

🔍 **Self-Check**: Scan for plugin version < 1.0.36. 🧪 Test REST endpoints for missing auth/CSRF headers when updating options.

Q: Is it fixed officially? (Patch/Mitigation)

🩹 **Fix**: Upgrade plugin to version **1.0.36** or higher. ✅ Official patch addresses the authorization flaw.

Q: What if no patch? (Workaround)

🚧 **No Patch?**: Disable the plugin immediately. 🛑 Block REST API access for this plugin via firewall/WAF rules.

Q: Is it urgent? (Priority Suggestion)

⚡ **Urgency**: **CRITICAL**. 🔥 High impact (Full Admin Takeover) + Low barrier (No Auth) = Immediate Action Required.

Question 1

What is this vulnerability? (Essence + Consequences)

Accepted Answer

🚨 **Essence**: Unauthenticated Arbitrary Options Update in WordPress Plugin 'Sitemap by click5'. 💥 **Consequences**: Attackers can change blog settings, create admin accounts, and **take over the entire blog**.

Question 2

Root Cause? (CWE/Flaw)

Accepted Answer

🛡️ **Root Cause**: Missing **Authorization** and **CSRF checks** on REST endpoints. The plugin fails to verify if the option being updated belongs to it.

Question 3

Who is affected? (Versions/Components)

Accepted Answer

📦 **Affected**: WordPress Plugin **Sitemap by click5**. 📉 **Version**: All versions **< 1.0.36**.

Question 4

What can hackers do? (Privileges/Data)

Accepted Answer

🕵️ **Attacker Actions**: Modify arbitrary options (e.g., `users_can_register`, `default_role`). 👑 **Result**: Create new **Admin Accounts** and gain full control.

Question 5

Is exploitation threshold high? (Auth/Config)

Accepted Answer

🔓 **Threshold**: **LOW**. 🚫 **Auth Required**: **None**. Unauthenticated attackers can exploit this directly.

Question 6

Is there a public Exp? (PoC/Wild Exploitation)

Accepted Answer

💣 **Exploit**: **YES**. 🔗 Public PoC available on GitHub (RandomRobbieBF) and Nuclei templates.

Question 7

How to self-check? (Features/Scanning)

Accepted Answer

🔍 **Self-Check**: Scan for plugin version < 1.0.36. 🧪 Test REST endpoints for missing auth/CSRF headers when updating options.

Question 8

Is it fixed officially? (Patch/Mitigation)

Accepted Answer

🩹 **Fix**: Upgrade plugin to version **1.0.36** or higher. ✅ Official patch addresses the authorization flaw.

Question 9

What if no patch? (Workaround)

Accepted Answer

🚧 **No Patch?**: Disable the plugin immediately. 🛑 Block REST API access for this plugin via firewall/WAF rules.

Question 10

Is it urgent? (Priority Suggestion)

Accepted Answer

⚡ **Urgency**: **CRITICAL**. 🔥 High impact (Full Admin Takeover) + Low barrier (No Auth) = Immediate Action Required.

Goal Reached Thanks to every supporter — we hit 100%!

CVE-2022-0952 — AI Deep Analysis Summary

Q1What is this vulnerability? (Essence + Consequences)

Q2Root Cause? (CWE/Flaw)

Q3Who is affected? (Versions/Components)

Q4What can hackers do? (Privileges/Data)

Q5Is exploitation threshold high? (Auth/Config)

Q6Is there a public Exp? (PoC/Wild Exploitation)

Q7How to self-check? (Features/Scanning)

Q8Is it fixed officially? (Patch/Mitigation)

Q9What if no patch? (Workaround)

Q10Is it urgent? (Priority Suggestion)

Continue exploring