{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-29423 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-29423 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-29423 is a low-severity vulnerability in Adam Skaat Countdown \u0026 Clock (WordPress plugin), published on 6 May 2022. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-29423 and fix it if it is affected.\n\nWhat it is: CVE-2022-29423 is a low-severity vulnerability in Adam Skaat Countdown \u0026 Clock (WordPress plugin), published on 6 May 2022. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-29423 in the wild and no public exploit code.\n\nAffected product: Adam Skaat Countdown \u0026 Clock (WordPress plugin). 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-2022-29423/ (Markdown: https://insights.sbomify.com/CVE-2022-29423/index.md)","id":"CVE-2022-29423","markdown":"https://insights.sbomify.com/CVE-2022-29423/index.md","name":"CVE-2022-29423","record":{"aliases":["GHSA-xccw-935f-5h48"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"Attackers can bypass the lock on Pro features in the Countdown \u0026 Clock WordPress plugin, gaining unauthorized access to premium functionality.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[{"product":"countdown_builder","vendor":"edmonsoft"}],"cvss":{"score":3.8,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-264","name":null}],"description":"Pro Features Lock Bypass vulnerability in Countdown \u0026 Clock plugin \u003c= 2.3.2 at WordPress.","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":"WordPress Countdown \u0026 Clock plugin \u003c= 2.3.2 - Pro Features Lock Bypass vulnerability","id":"CVE-2022-29423","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in Image Hover Effects Ultimate (WordPress plugin)","id":"CVE-2022-29424"},"packages":[],"prev":{"headline":"Cross-site scripting in Countdown \u0026 Clock (WordPress plugin)","id":"CVE-2022-29422"},"products":["Countdown \u0026 Clock (WordPress plugin)"],"published":"2022-05-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":5.4,"headline":"Missing authorization in Countdown, Coming Soon, Maintenance – Countdown \u0026 Clock","id":"CVE-2024-2017","kev_date_added":null,"published":"2024-06-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"}],"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-28","vendors":["Adam Skaat"]},"summary":"Attackers can bypass the lock on Pro features in the Countdown \u0026 Clock WordPress plugin, gaining unauthorized access to premium functionality.","url":"https://insights.sbomify.com/CVE-2022-29423/"}