Goal Reached Thanks to every supporter โ€” we hit 100%!

Goal: 1000 CNY ยท Raised: 1336 CNY

100%

CVE-2025-8572 โ€” AI Deep Analysis Summary

CVSS 9.8 ยท Critical

Q1What is this vulnerability? (Essence + Consequences)

๐Ÿšจ **Essence**: A critical flaw in **Truelysell Core** plugin allows unauthorized role assignment. ๐Ÿ“‰ **Consequences**: Attackers can create admin-level accounts without permission, leading to full site takeover.

Q2Root Cause? (CWE/Flaw)

๐Ÿ›ก๏ธ **Root Cause**: **CWE-269** (Improper Privilege Management). The plugin fails to validate the `user_role` parameter during user registration. ๐Ÿ› **Flaw**: Weak input sanitization allows privilege escalation.

Q3Who is affected? (Versions/Components)

๐Ÿ“ฆ **Affected**: **Truelysell Core** plugin version **1.8.7 and earlier**. ๐Ÿข **Vendor**: Dreamstechnologies. ๐ŸŒ **Platform**: WordPress sites using this specific booking theme/plugin.

Q4What can hackers do? (Privileges/Data)

๐Ÿ’€ **Attacker Action**: Create new user accounts with **elevated privileges** (e.g., Admin). ๐Ÿ”“ **Impact**: Full control over the WordPress site, data theft, and malicious code injection.

Q5Is exploitation threshold high? (Auth/Config)

๐Ÿ”“ **Threshold**: **LOW**. CVSS indicates **No Auth** (PR:N) required. ๐ŸŒ **Access**: Network accessible (AV:N), Low complexity (AC:L). Anyone can exploit this remotely.

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

๐Ÿ’ป **Exploit**: Yes, public PoC available. ๐Ÿ”— **Link**: [GitHub PoC](https://github.com/richardpaimu34/CVE-2025-8572). โš ๏ธ **Status**: Wild exploitation risk is high due to simple vector.

Q7How to self-check? (Features/Scanning)

๐Ÿ” **Check**: Scan for **Truelysell Core** plugin version โ‰ค 1.8.7. ๐Ÿ“ **Feature**: Look for user registration endpoints accepting `user_role` parameters without server-side validation.

Q8Is it fixed officially? (Patch/Mitigation)

๐Ÿ› ๏ธ **Fix**: Update **Truelysell Core** to the latest version immediately. ๐Ÿ“ข **Source**: Check vendor (Dreamstechnologies) or WordPress repository for patched releases.

Q9What if no patch? (Workaround)

๐Ÿšง **Workaround**: If patching is delayed, **disable public registration** or restrict user roles via server-side rules. ๐Ÿ›‘ Block access to registration endpoints if possible.

Q10Is it urgent? (Priority Suggestion)

๐Ÿ”ฅ **Priority**: **CRITICAL**. CVSS Score is High (likely 9.8+). ๐Ÿš€ **Action**: Patch immediately. This is a remote, unauthenticated privilege escalation. Do not wait.