सपोर्ट बोर्ड <= 3.8.0 - प्रमाणीकरण रहित मनमाना फ़ाइल विलोपन

The primary impact of CVE-2025-4828 is the ability for an attacker to delete arbitrary files on the server hosting the WordPress site. This is a severe risk because the attacker doesn't need authentication to exploit this vulnerability, especially when chained with CVE-2025-4855. Deleting wp-config.php would effectively disable the WordPress site and potentially allow the attacker to gain control of the database and the server itself. The blast radius extends to any sensitive data stored within the WordPress installation, including user credentials, customer data, and potentially database backups. This vulnerability shares similarities with other file deletion vulnerabilities where the attacker can manipulate file paths to gain unauthorized access or control.

WordPress websites using the Support Board plugin, particularly those with shared hosting environments or legacy configurations, are at significant risk. Sites with weak file permissions or inadequate security plugins are especially vulnerable. Any site relying on the Support Board plugin for file management or user support features should be considered at risk.

• wordpress / plugin: Use wp-cli plugin update --all to check for available updates. • wordpress / plugin: Search plugin files for the sbfiledelete function and look for any instances of unsanitized user input being used in file path construction.

grep -r 'sb_file_delete' /var/www/wordpress/wp-content/plugins/support-board/

• generic web: Monitor web server access logs for requests containing suspicious file paths or deletion attempts, especially those targeting files within the WordPress plugin directory. • generic web: Check WordPress plugin directory permissions to ensure they are restricted to the WordPress user account.

1. 2025-07-08Disclosure

   disclosure

1. आरक्षित2025-05-16
2. प्रकाशित2025-07-08
3. संशोधित2026-04-08
4. EPSS अद्यतन2026-03-23

The immediate mitigation for CVE-2025-4828 is to upgrade the WordPress Support Board plugin to a version that addresses the vulnerability. Unfortunately, a fixed version is not yet available. As a workaround, restrict file upload permissions to the WordPress user account and implement strict file access controls on the server. Consider using a WordPress security plugin with file integrity monitoring capabilities to detect unauthorized file modifications. Implement a Web Application Firewall (WAF) with rules to block requests containing suspicious file paths or deletion attempts. After upgrading (or implementing workarounds), verify the plugin's functionality and file integrity by manually checking for any unexpected file deletions or modifications.