# CVE-2026-122151: Presenton User Configuration user-config JSON.parse 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:** 5 Nov 2026
- **Updated:** 5 Nov 2026
- **Also known as:** GHSA-m6p5-h26j-pxv5

## What is CVE-2026-122151?

CVE-2026-122151 is a medium-severity vulnerability in Presenton, published on 5 Nov 2026. 

### Official description

A security vulnerability has been detected in Presenton up to 0.9.11-beta. Impacted is the function JSON.parse of the file /api/user-config of the component User Configuration Handler. Such manipulation leads to cross-site request forgery. It is possible to launch the attack remotely. The exploit has been disclosed publicly and may be used. Upgrading to version 0.9.12-beta is recommended to address this issue. The name of the patch is 44c8a61122b21f17642d717b0c4d6f2c54c0f180. It is recommended to upgrade the affected component.

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

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


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

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

## Is CVE-2026-122151 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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