# CVE-2026-92383: PbootCMS User Management UserController.php mod cross-site request forgery


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-g65h-8grw-v433

## What is CVE-2026-92383?

CVE-2026-92383 is a medium-severity vulnerability in PbootCMS, published on 16 Sep 2026. 

### Official description

A security vulnerability has been detected in PbootCMS up to 3.2.24. This vulnerability affects the function UserController::del/UserController::mod of the file apps/admin/controller/system/UserController.php of the component User Management. Such manipulation leads to cross-site request forgery. The attack may be performed from remote. The exploit has been disclosed publicly and may be used. Upgrading to version 3.2.25 is able to resolve this issue. The name of the patch is c25241a0964742cefb7f698efbb6c38b868d6ff7. It is advisable to upgrade the affected component.

Weakness: CWE-862 (Missing Authorization), CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-92383 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92383 is a medium-severity vulnerability in PbootCMS, published on 16 Sep 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92383 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-92383/ (Markdown: https://insights.sbomify.com/CVE-2026-92383/index.md)
```

## Sources

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

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