# CVE-2026-82603: SeaCMS Comment Cache member.php del_pl path traversal

> Remote attackers can exploit a path traversal vulnerability in SeaCMS comment cache handling to read or modify arbitrary files.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2026
- **Updated:** 1 Sep 2026
- **Also known as:** GHSA-w79p-9336-45xf

## What is CVE-2026-82603?

CVE-2026-82603 is a medium-severity path traversal vulnerability in SeaCMS, published on 31 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was detected in SeaCMS up to 13.6. This issue affects some unknown processing of the file /member.php?action=del_pl of the component Comment Cache. The manipulation of the argument itype/vid results in path traversal. The attack may be launched remotely. The exploit is now public and may be used.

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

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


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

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

## Is CVE-2026-82603 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82603 is a medium-severity path traversal vulnerability in SeaCMS, published on 31 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82603 exists.

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

## Sources

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

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