WordPress security changelog
HIGH CVE-2020-8658 Modified

Htaccess: Cross-site request forgery

Htaccess is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.

CVE / CNA score 8.8 CVSS · cve@mitre.org
NVD score 8.8 CVSS 3.1 · nvd@nist.gov
Component
Htaccess
Plugin slug
htaccess
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Feb 06, 2020
Weakness
CWE-352 — Cross-Site Request Forgery (CSRF)

This CVE was published Feb 06, 2020 and is one of 2 known issues for this plugin.

Update, patch or deactivate.

Update Htaccess to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Technical description

The BestWebSoft Htaccess plugin through 1.8.1 for WordPress allows wp-admin/admin.php?page=htaccess.php&action=htaccess_editor CSRF. The flag htccss_nonce_name passes the nonce to WordPress but the plugin does not validate it correctly, resulting in a wrong implementation of anti-CSRF protection. In this way, an attacker is able to direct the victim to a malicious web page that modifies the .htaccess file, and takes control of the website.

NVD vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Primary and upstream sources