{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-2270 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-2270 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-2270 is a high-severity path traversal vulnerability in adamskaat Countdown, Coming Soon, Maintenance – Countdown \u0026 Clock, published on 4 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-2270 and fix it if it is affected.\n\nWhat it is: CVE-2025-2270 is a high-severity path traversal vulnerability in adamskaat Countdown, Coming Soon, Maintenance – Countdown \u0026 Clock, published on 4 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-2270 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-2025-2270/ (Markdown: https://insights.sbomify.com/CVE-2025-2270/index.md)","id":"CVE-2025-2270","markdown":"https://insights.sbomify.com/CVE-2025-2270/index.md","name":"CVE-2025-2270","record":{"aliases":["GHSA-842m-396f-hgpg"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can exploit a local file inclusion vulnerability in the Countdown \u0026 Clock WordPress plugin to execute arbitrary PHP code or read sensitive data.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"The Countdown, Coming Soon, Maintenance – Countdown \u0026 Clock plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 2.8.9.1 via the createCdObj function. This makes it possible for unauthenticated attackers to include and execute files with the specific filenames on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in some cases.","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":"Countdown, Coming Soon, Maintenance – Countdown \u0026 Clock \u003c= 2.8.9.1 - Unauthenticated Limited Local File Inclusion","id":"CVE-2025-2270","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"IDOR in Issuetrak NewAuditID parameter via Inv_PopTrakXShow.asp","id":"CVE-2025-2271"},"packages":[],"prev":{"headline":"Cross-site scripting in Photo Gallery by 10Web – Mobile-Friendly Image Gallery","id":"CVE-2025-2269"},"products":["Countdown, Coming Soon, Maintenance – Countdown \u0026 Clock"],"published":"2025-04-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"total"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["adamskaat"]},"summary":"Unauthenticated attackers can exploit a local file inclusion vulnerability in the Countdown \u0026 Clock WordPress plugin to execute arbitrary PHP code or read sensitive data.","url":"https://insights.sbomify.com/CVE-2025-2270/"}