# CVE-2026-92381: PbootCMS Template Rendering ContentController.php decode_string cross site scripting

> Remote attackers can execute arbitrary scripts via XSS in PbootCMS template rendering, potentially compromising user sessions and data.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-4c2q-5fw3-3mm8

## What is CVE-2026-92381?

CVE-2026-92381 is a medium-severity cross-site scripting vulnerability in PbootCMS, published on 16 Sep 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

A weakness has been identified in PbootCMS up to 3.2.22. This affects the function decode_string of the file apps/admin/controller/content/ContentController.php of the component Template Rendering. This manipulation of the argument Title causes cross site scripting. The attack is possible to be carried out remotely. The exploit has been made available to the public and could be used for attacks. The reported GitHub issue was closed with the reason "completed".

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-92381 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92381 is a medium-severity cross-site scripting vulnerability in PbootCMS, published on 16 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92381 exists.

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

## Sources

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

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