# CVE-2026-40038: Pachno 1.0.6 Stored Cross-Site Scripting via Multiple Parameters

> Attackers can inject malicious scripts into multiple parameters, leading to arbitrary code execution in victim browsers via stored XSS.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Apr 2026
- **Updated:** 24 May 2026
- **Also known as:** GHSA-fpfp-p6p5-q4rm

## What is CVE-2026-40038?

CVE-2026-40038 is a medium-severity cross-site scripting vulnerability in Pachno, published on 13 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Pachno 1.0.6 contains a stored cross-site scripting vulnerability that allows attackers to execute arbitrary HTML and script code by injecting malicious payloads into POST parameters. Attackers can inject scripts through the value, comment_body, article_content, description, and message parameters across multiple controllers, which are stored in the database and executed in users' browser sessions due to improper sanitization via Request::getRawParameter() or Request::getParameter() calls.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-40038 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-40038 is a medium-severity cross-site scripting vulnerability in Pachno, published on 13 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-40038 in the wild and no public exploit code.

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

## Sources

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

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