CVE-2025-29010

4.3 MEDIUM

📋 TL;DR

CVE-2025-29010 is a missing authorization vulnerability in the Behance Portfolio Manager WordPress plugin that allows attackers to bypass access controls and perform unauthorized actions. This affects all WordPress sites running the plugin from any version through 1.7.4. The vulnerability enables privilege escalation and unauthorized data access.

💻 Affected Systems

Products:
  • Behance Portfolio Manager (WordPress plugin)
Versions: n/a through 1.7.4
Operating Systems: All operating systems running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Affects all WordPress installations using the vulnerable plugin versions. No special configuration required for exploitation.

⚠️ 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 gain administrative access to WordPress sites, modify content, install malicious plugins/themes, steal sensitive data, or completely compromise the website.

🟠

Likely Case

Unauthorized users could modify portfolio content, access private portfolio items, or perform actions reserved for authenticated users without proper permissions.

🟢

If Mitigated

With proper network segmentation and least privilege principles, impact would be limited to the specific WordPress instance without lateral movement.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires some WordPress knowledge but is straightforward once the vulnerability is understood. Attackers need at least some level of access to the WordPress interface.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 1.7.5 or later

Vendor Advisory: https://patchstack.com/database/wordpress/plugin/portfolio-manager-powered-by-behance/vulnerability/wordpress-behance-portfolio-manager-1-7-4-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 'Behance Portfolio Manager'. 4. Click 'Update Now' if update available. 5. If no update available, download version 1.7.5+ from WordPress repository and manually update.

🔧 Temporary Workarounds

Disable vulnerable plugin

all

Temporarily disable the Behance Portfolio Manager plugin until patched

wp plugin deactivate portfolio-manager-powered-by-behance

Restrict plugin access

all

Use WordPress security plugins to restrict access to plugin functionality

🧯 If You Can't Patch

  • Implement strict network access controls to limit who can access the WordPress admin interface
  • Enable WordPress security plugins with access control features and audit all user permissions

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin panel → Plugins → Behance Portfolio Manager version. If version is 1.7.4 or earlier, system is vulnerable.

Check Version:

wp plugin get portfolio-manager-powered-by-behance --field=version

Verify Fix Applied:

Verify plugin version is 1.7.5 or later in WordPress admin panel. Test portfolio management functions with non-admin users to ensure proper access controls.

📡 Detection & Monitoring

Log Indicators:

  • Unauthorized access attempts to portfolio management endpoints
  • Non-admin users performing portfolio modifications
  • Failed authorization checks in WordPress debug logs

Network Indicators:

  • Unusual POST requests to /wp-admin/admin-ajax.php with portfolio-related actions
  • Non-admin IP addresses accessing admin functions

SIEM Query:

source="wordpress.log" AND ("portfolio-manager" OR "behance") AND ("unauthorized" OR "permission denied" OR "admin-ajax.php")

🔗 References

📤 Share & Export