{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-13336 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-13336 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-13336 is a medium-severity vulnerability in exeebit Disable Auto Updates, published on 19 Feb 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-13336 and fix it if it is affected.\n\nWhat it is: CVE-2024-13336 is a medium-severity vulnerability in exeebit Disable Auto Updates, published on 19 Feb 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-13336 in the wild and no public exploit code.\n\nAffected product: exeebit Disable Auto Updates. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-13336/ (Markdown: https://insights.sbomify.com/CVE-2024-13336/index.md)","id":"CVE-2024-13336","markdown":"https://insights.sbomify.com/CVE-2024-13336/index.md","name":"CVE-2024-13336","record":{"aliases":["GHSA-4r48-94p2-qwq4"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"An attacker can trick a WordPress admin into disabling auto-updates via CSRF, leaving the site vulnerable to future exploits.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"disable_auto_updates","vendor":"exeebit"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Disable Auto Updates \u003c= 1.4 - Cross-Site Request Forgery to Auto-update Disable","id":"CVE-2024-13336","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site request forgery in Clearfy Cache – WordPress optimization plugin, Minify HTML, CSS \u0026 JS, Defer","id":"CVE-2024-13337"},"packages":[],"prev":{"headline":"Missing authorization in Spexo Addons for Elementor – Elementor Widgets, Mega Menu, Popup Builder, Template Kits and Starter Templates for Elementor","id":"CVE-2024-13335"},"products":["Disable Auto Updates"],"published":"2025-02-19","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["exeebit"]},"summary":"An attacker can trick a WordPress admin into disabling auto-updates via CSRF, leaving the site vulnerable to future exploits.","url":"https://insights.sbomify.com/CVE-2024-13336/"}