CVE-2025-10049

7.2 HIGH

📋 TL;DR

This vulnerability allows authenticated attackers with Administrator-level access or higher to upload arbitrary files to WordPress sites using the Responsive Filterable Portfolio plugin, potentially leading to remote code execution. It affects all versions of the plugin up to and including 1.0.24. Users of this plugin on WordPress installations are at risk if attackers gain administrative credentials.

💻 Affected Systems

Products:
  • Responsive Filterable Portfolio plugin for WordPress
Versions: All versions up to and including 1.0.24
Operating Systems: Any OS running WordPress (e.g., Linux, Windows)
Default Config Vulnerable: ⚠️ Yes
Notes: Requires authenticated attacker with Administrator-level access or higher; default plugin configurations are vulnerable.

⚠️ 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 achieve remote code execution, compromising the entire server, stealing data, defacing the site, or installing malware.

🟠

Likely Case

Attackers upload malicious files like web shells to execute arbitrary commands, leading to data breaches or site takeover.

🟢

If Mitigated

With proper access controls and file validation, impact is limited to unauthorized file uploads without code execution.

🌐 Internet-Facing: HIGH, as WordPress sites are typically internet-facing, making them accessible to attackers who obtain admin credentials.
🏢 Internal Only: MEDIUM, as internal attackers with admin access could exploit it, but network segmentation might reduce exposure.

🎯 Exploit Status

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

Exploitation requires admin credentials but is straightforward once access is gained; no public proof-of-concept confirmed, but weaponization is likely due to the severity.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 1.0.25

Vendor Advisory: https://plugins.trac.wordpress.org/changeset?old_path=/responsive-filterable-portfolio/tags/1.0.24&new_path=/responsive-filterable-portfolio/tags/1.0.25

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Go to Plugins > Installed Plugins. 3. Find 'Responsive Filterable Portfolio' and update to version 1.0.25. 4. Verify update completes successfully.

🔧 Temporary Workarounds

Disable plugin

all

Temporarily deactivate the Responsive Filterable Portfolio plugin to prevent exploitation.

wp plugin deactivate responsive-filterable-portfolio

Restrict file uploads via web server

linux

Configure web server (e.g., Apache, Nginx) to block uploads of executable files in the plugin's upload directory.

# Example for Apache: add to .htaccess in uploads folder
<FilesMatch "\.(php|phtml|exe|sh)$">
  Order Allow,Deny
  Deny from all
</FilesMatch>

🧯 If You Can't Patch

  • Enforce strong authentication and access controls for admin accounts to reduce risk of credential compromise.
  • Implement web application firewall (WAF) rules to block suspicious file uploads targeting the HdnMediaSelection_image field.

🔍 How to Verify

Check if Vulnerable:

Check the plugin version in WordPress admin under Plugins > Installed Plugins; if version is 1.0.24 or lower, it is vulnerable.

Check Version:

wp plugin get responsive-filterable-portfolio --field=version

Verify Fix Applied:

After updating, confirm the plugin version is 1.0.25 or higher in the same location.

📡 Detection & Monitoring

Log Indicators:

  • Unusual file uploads in WordPress logs, especially to paths related to the plugin or with non-image file extensions.
  • Admin login attempts from unexpected IP addresses.

Network Indicators:

  • HTTP POST requests to plugin endpoints with file uploads containing executable content.

SIEM Query:

source="wordpress.log" AND ("HdnMediaSelection_image" OR "responsive-filterable-portfolio") AND ("upload" OR ".php" OR ".exe")

🔗 References

📤 Share & Export