# CVE-2026-132601: SEO Panel Website Import website.ctrl.php mime_content_type unrestricted upload


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 19 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-xmch-m9pc-ch8h

## What is CVE-2026-132601?

CVE-2026-132601 is a medium-severity vulnerability in SEO Panel, published on 19 Nov 2026. 

### Official description

A security vulnerability has been detected in SEO Panel 6.0.0. This affects the function mime_content_type of the file controllers/website.ctrl.php of the component Website Import. Such manipulation of the argument website_csv_file leads to unrestricted upload. It is possible to launch the attack remotely. The exploit has been disclosed publicly and may be used. Upgrading to version 7.0.0 mitigates this issue. The name of the patch is 2a2d4aeb718177327b0cd8ce17e2f40328772127. You should upgrade the affected component.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Seo Panel.

CPE match criteria (CPE 2.3):

- `cpe:2.3:a:seo_panel:seo_panel:*:*:*:*:*:*:*:*` from 6.0.0 up to 6.0.0

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

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

## Is CVE-2026-132601 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-132601 is a medium-severity vulnerability in SEO Panel, published on 19 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-132601 exists.

Affected product: SEO Panel. 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-132601/ (Markdown: https://insights.sbomify.com/CVE-2026-132601/index.md)
```

## Sources

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

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