# CVE-2025-67992: WordPress PatioTime theme < 2.1 - Local File Inclusion vulnerability

> Attackers can exploit a local file inclusion vulnerability in the PatioTime theme to read sensitive files or execute arbitrary code.

- **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:** 20 Feb 2026
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-7gx4-4vpm-w576

## What is CVE-2025-67992?

CVE-2025-67992 is a high-severity path traversal vulnerability in LoftOcean PatioTime, published on 20 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in LoftOcean PatioTime patiotime allows PHP Local File Inclusion.This issue affects PatioTime: from n/a through < 2.1.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

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


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

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

## Is CVE-2025-67992 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-67992 is a high-severity path traversal vulnerability in LoftOcean PatioTime, published on 20 Feb 2026. 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-67992 in the wild and no public exploit code.

Affected product: LoftOcean PatioTime. 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-67992/ (Markdown: https://insights.sbomify.com/CVE-2025-67992/index.md)
```

## Sources

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

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