WordPress security changelog
MEDIUM CVE-2024-13336 Analyzed

Disable Auto Updates: Cross-site request forgery

Disable Auto Updates is affected by cross-site request forgery. The vulnerable path is reachable without authentication. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.

CVE / CNA score 4.3 CVSS 3.1 · security@wordfence.com
NVD score 4.3 CVSS 3.1 · nvd@nist.gov
Component
Disable Auto Updates
Plugin slug
disable-auto-updates
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Feb 19, 2025
Weakness
CWE-352 — Cross-Site Request Forgery (CSRF)

This CVE was published Feb 19, 2025 and is one of 1 known issue for this plugin.

Update, patch or deactivate.

Update Disable Auto Updates 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 Disable Auto Updates plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.4. This is due to missing or incorrect nonce validation on the 'disable-auto-updates' page. This makes it possible for unauthenticated attackers to disable all auto updates via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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

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

Primary and upstream sources