CVE-2023-29173

5.3 MEDIUM

📋 TL;DR

This CVE describes a missing authorization vulnerability in the AWESOME TOGI Product Category Tree WordPress plugin that allows attackers to exploit incorrectly configured access control security levels. Attackers can perform unauthorized actions that should require proper authentication. This affects all WordPress sites running Product Category Tree plugin versions up to 2.5.

💻 Affected Systems

Products:
  • AWESOME TOGI Product Category Tree WordPress Plugin
Versions: n/a through 2.5
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Affects WordPress installations with the vulnerable plugin version installed and activated.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could modify product categories, alter site structure, or potentially escalate privileges to gain administrative access to the WordPress site.

🟠

Likely Case

Unauthorized users could manipulate product category trees, potentially disrupting e-commerce functionality or causing site content issues.

🟢

If Mitigated

With proper access controls and authentication requirements, only authorized administrators could modify product categories as intended.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Missing authorization vulnerabilities typically require minimal technical skill to exploit once the attack vector is identified.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 2.6 or later

Vendor Advisory: https://patchstack.com/database/wordpress/plugin/product-category-tree/vulnerability/wordpress-product-category-tree-plugin-2-5-broken-access-control-vulnerability?_s_id=cve

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins → Installed Plugins. 3. Find 'Product Category Tree' plugin. 4. Click 'Update Now' if update available. 5. If no update available, deactivate and delete plugin, then install latest version from WordPress repository.

🔧 Temporary Workarounds

Temporary Plugin Deactivation

all

Disable the vulnerable plugin until patched version is available

wp plugin deactivate product-category-tree

Access Restriction via .htaccess

linux

Restrict access to plugin files via web server configuration

# Add to .htaccess in WordPress root:
<FilesMatch "product-category-tree\.php">
Order Deny,Allow
Deny from all
</FilesMatch>

🧯 If You Can't Patch

  • Implement strict network access controls to limit who can access the WordPress admin interface
  • Enable WordPress security plugins that monitor and block unauthorized access attempts

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin → Plugins → Installed Plugins for Product Category Tree version 2.5 or earlier

Check Version:

wp plugin get product-category-tree --field=version

Verify Fix Applied:

Verify plugin version is 2.6 or later in WordPress admin panel

📡 Detection & Monitoring

Log Indicators:

  • Unauthorized POST requests to product-category-tree endpoints
  • Failed authentication attempts followed by successful category modifications

Network Indicators:

  • HTTP requests to /wp-content/plugins/product-category-tree/ without proper authentication headers

SIEM Query:

source="wordpress.log" AND (uri_path="/wp-content/plugins/product-category-tree/" OR plugin="product-category-tree") AND (response_code=200 OR response_code=302) AND NOT user_role="administrator"

🔗 References

📤 Share & Export