CVE-2024-13336: Disable Auto Updates <= 1.4 - Cross-Site Request Forgery to Auto-update Disable
First published: Wed Feb 19 2025(Updated: )
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.
Credit: security@wordfence.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| WordPress Disable Auto Updates | <=1.4 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2024-13336?
CVE-2024-13336 is classified as a medium severity vulnerability.
How do I fix CVE-2024-13336?
To mitigate CVE-2024-13336, update the Disable Auto Updates plugin to version 1.5 or later.
What kind of vulnerability is CVE-2024-13336?
CVE-2024-13336 is a Cross-Site Request Forgery (CSRF) vulnerability.
Who is affected by CVE-2024-13336?
All versions of the Disable Auto Updates plugin for WordPress up to and including 1.4 are affected by CVE-2024-13336.
Can CVE-2024-13336 be exploited remotely?
Yes, CVE-2024-13336 can be exploited by unauthenticated attackers remotely.
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/title
- agent/type
- agent/references
- agent/description
- agent/first-publish-date
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- agent/author
- agent/last-modified-date
- agent/severity
- agent/source
- agent/tags
- agent/event
- vendor/wordpress
- canonical/wordpress disable auto updates