# CVE-2025-2270: Countdown, Coming Soon, Maintenance – Countdown & Clock <= 2.8.9.1 - Unauthenticated Limited Local File Inclusion

> Unauthenticated attackers can exploit a local file inclusion vulnerability in the Countdown & Clock WordPress plugin to execute arbitrary PHP code or read sensitive data.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Apr 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-842m-396f-hgpg

## What is CVE-2025-2270?

CVE-2025-2270 is a high-severity path traversal vulnerability in adamskaat Countdown, Coming Soon, Maintenance – Countdown & Clock, published on 4 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Countdown, Coming Soon, Maintenance – Countdown & 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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-2270?


## How do I fix CVE-2025-2270?

No fix has been published for CVE-2025-2270 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-2270 being exploited?

There is no known exploitation of CVE-2025-2270 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2270 and fix it if it is affected.

What it is: CVE-2025-2270 is a high-severity path traversal vulnerability in adamskaat Countdown, Coming Soon, Maintenance – Countdown & Clock, published on 4 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-2270 in the wild and no public exploit code.

Affected product: adamskaat Countdown, Coming Soon, Maintenance – Countdown & Clock. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-2270/ (Markdown: https://insights.sbomify.com/CVE-2025-2270/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-2270
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-2270
- OSV: https://osv.dev/vulnerability/CVE-2025-2270

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-2270/
Summaries are generated and may contain mistakes; the official description above is the record.