# CVE-2026-120207: Thelia Page Module before 2.0.4 CSRF via Page Tag, Document and Image Delete Routes


- **Severity:** High 7.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 31 Oct 2026
- **Updated:** 6 Nov 2026
- **Also known as:** GHSA-h2jf-7chq-2q39, GHSA-whqr-4v2h-6jhc

## What is CVE-2026-120207?

CVE-2026-120207 is a high-severity vulnerability in Thelia Page Module, published on 31 Oct 2026. 

### Official description

Thelia Page Module before 2.0.4 contains a cross-site request forgery vulnerability that allows remote attackers to delete page tags, documents and images by abusing back-office delete routes lacking CSRF tokens and permission checks. Attackers can lure a logged-in administrator into navigating to crafted GET requests that walk sequential ids, removing TheliaLibrary images, their files and variants across pages, products and categories.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-120207 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120207 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120207 is a high-severity vulnerability in Thelia Page Module, published on 31 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120207 exists.

Affected product: Thelia Page Module. 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-120207/ (Markdown: https://insights.sbomify.com/CVE-2026-120207/index.md)
```

## Sources

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

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