# CVE-2026-66670: WordPress Måne theme <= 1.7 - Local File Inclusion vulnerability

> Unauthenticated attackers can exploit a local file inclusion vulnerability in the Måne WordPress 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:** 24 Aug 2026
- **Updated:** 24 Aug 2026
- **Also known as:** GHSA-97pr-h63m-phh4

## What is CVE-2026-66670?

CVE-2026-66670 is a high-severity path traversal vulnerability in Elated-Themes Måne, published on 24 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unauthenticated Local File Inclusion in Måne <= 1.7 versions.

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

## Which versions are affected by CVE-2026-66670?


## How do I fix CVE-2026-66670?

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

## Is CVE-2026-66670 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-66670 and fix it if it is affected.

What it is: CVE-2026-66670 is a high-severity path traversal vulnerability in Elated-Themes Måne, published on 24 Aug 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-2026-66670 in the wild and no public exploit code.

Affected product: Elated-Themes Måne. 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-2026-66670/ (Markdown: https://insights.sbomify.com/CVE-2026-66670/index.md)
```

## Sources

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

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