{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-2017 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-2017 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-2017 is a medium-severity missing authorization vulnerability in adamskaat Countdown, Coming Soon, Maintenance – Countdown \u0026 Clock, published on 6 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-2017 and fix it if it is affected.\n\nWhat it is: CVE-2024-2017 is a medium-severity missing authorization vulnerability in adamskaat Countdown, Coming Soon, Maintenance – Countdown \u0026 Clock, published on 6 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-2017 in the wild and no public exploit code.\n\nAffected product: adamskaat Countdown, Coming Soon, Maintenance – Countdown \u0026 Clock. 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-2017/ (Markdown: https://insights.sbomify.com/CVE-2024-2017/index.md)","id":"CVE-2024-2017","markdown":"https://insights.sbomify.com/CVE-2024-2017/index.md","name":"CVE-2024-2017","record":{"aliases":["GHSA-pcmg-m577-c53m"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","other"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated subscribers can bypass authorization checks to inject PHP objects and modify countdown statuses in the Countdown \u0026 Clock WordPress plugin.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"countdown_builder","vendor":"edmonsoft"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"The Countdown, Coming Soon, Maintenance – Countdown \u0026 Clock plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on the conditionsRow and switchCountdown functions in all versions up to, and including, 2.7.8. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject PHP Objects and modify the status of countdowns.","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":"Missing authorization in Countdown, Coming Soon, Maintenance – Countdown \u0026 Clock","id":"CVE-2024-2017","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2024"},"n_packages":0,"n_references":5,"next":{"headline":"WP Activity Log Premium \u003c= 4.6.4 - Authenticated (Subscriber+) SQL Injection","id":"CVE-2024-2018"},"packages":[],"prev":{"headline":"ZhiCms setcontroller.php index code injection","id":"CVE-2024-2016"},"products":["Countdown, Coming Soon, Maintenance – Countdown \u0026 Clock"],"published":"2024-06-06","related":[{"cvss_score":5.9,"headline":"WordPress Countdown \u0026 Clock plugin \u003c= 2.3.2 - Auth. Stored Cross-Site Scripting (XSS) vulnerability","id":"CVE-2022-29420","kev_date_added":null,"published":"2022-05-06"},{"cvss_score":4.8,"headline":"Cross-site scripting in Countdown \u0026 Clock (WordPress plugin)","id":"CVE-2022-29422","kev_date_added":null,"published":"2022-05-06"},{"cvss_score":4.7,"headline":"WordPress Countdown \u0026 Clock plugin \u003c= 2.3.2 - Reflected Cross-Site Scripting (XSS) vulnerability","id":"CVE-2022-29421","kev_date_added":null,"published":"2022-05-06"},{"cvss_score":3.8,"headline":"WordPress Countdown \u0026 Clock plugin \u003c= 2.3.2 - Pro Features Lock Bypass vulnerability","id":"CVE-2022-29423","kev_date_added":null,"published":"2022-05-06"}],"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":["adamskaat"]},"summary":"Authenticated subscribers can bypass authorization checks to inject PHP objects and modify countdown statuses in the Countdown \u0026 Clock WordPress plugin.","url":"https://insights.sbomify.com/CVE-2024-2017/"}